Golf

What is Golf?

Golf is a framework for building MCP (Model Context Protocol) servers. It allows developers to define server capabilities—tools, prompts, and resources—as simple Python files within a conventional directory structure, then automatically discovers and compiles them into a runnable MCP server. Golf is designed for Python developers who want to create MCP servers with minimal boilerplate, and includes built-in authentication, utilities for LLM interactions, and automatic telemetry.

How to use Golf?

Install Golf with pip install golf-mcp (Python 3.10+ required). Initialize a project using golf init your-project-name. Run the development server with golf build dev && golf run. Components are defined in tools/, resources/, and prompts/ directories; each Python file defines one component, with its module docstring serving as the description. Authentication is configured in an auth.py file using the configure_auth function.

Key features of Golf

• Automatic discovery and compilation of tools, prompts, and resources.
• Built-in authentication: JWT, OAuth Server, API key, and development tokens.
• OpenTelemetry integration for tracing.
• CLI scaffolding with golf init and golf run.
• Support for multiple transports: SSE, Streamable HTTP, and stdio.
• Telemetry with anonymous usage data and opt-out capability.

Use cases of Golf

• Rapidly prototyping an MCP server for an AI assistant that needs custom tools.
• Building a production-ready MCP server with enterprise-grade authentication.
• Creating a modular MCP server where capabilities are organized in separate files.
• Developing an MCP server with built-in monitoring via OpenTelemetry.
• Teaching or learning MCP server development with a simplified structure.

FAQ from Golf

What Python version is required?

Python 3.10 or later is recommended.

How do I install Golf?

Install it using pip: pip install golf-mcp.

What authentication options does Golf support?

Golf supports JWT, OAuth Server mode, API key (static tokens), and development tokens. Authentication is configured in an auth.py file using the configure_auth function.

Can I disable telemetry?

Yes. Run golf telemetry disable to permanently disable anonymous usage data collection. You can also use --no-telemetry with any command, or re-enable telemetry with golf telemetry enable.

Where are component IDs derived from?

Component IDs are automatically derived from the file path. For example, tools/hello.py becomes hello, and tools/payments/submit.py becomes submit_payments (filename followed by reversed parent directories under the main category, joined by underscores).