@DanKornas: Building an MCP server shouldn’t mean hand-wiring component discovery, schemas, authentication, and transport plumbing.…
Summary
Golf is a new open-source Python framework that simplifies building MCP servers by automatically discovering and compiling file-based tools, prompts, and resources, with schema inference, auth options, and multiple transports.
View Cached Full Text
Cached at: 07/31/26, 02:46 AM
Building an MCP server shouldn’t mean hand-wiring component discovery, schemas, authentication, and transport plumbing.
Golf is a Python framework for developers building MCP server applications.
It helps you turn structured Python files into a runnable MCP server by automatically discovering, parsing, and compiling tools, prompts, and resources.
Key features: • File-based components – define each tool, prompt, or resource in a conventional project directory. • Schema inference – derive parameters from function signatures and outputs from Pydantic models. • Project CLI – scaffold with golf init, then build and run the server locally. • Authentication options – configure JWT, OAuth server mode, API keys, or development tokens. • Multiple transports – choose SSE, streamable HTTP, or stdio, with optional OpenTelemetry tracing.
It’s open-source (Apache 2.0 license).
Link in the reply
Similar Articles
@DanKornas: Finding an MCP server is easy. Choosing one with the right access model is the hard part. Awesome MCP Servers is a cura…
Dan Kornas highlights a curated directory of Model Context Protocol (MCP) servers, grouping implementations by job and linking to supported hosts like Claude Desktop, Cursor, VS Code, and Zed. The open-source directory includes security guidance and official markers.
@DanKornas: Running several MCP servers separately gets messy fast. MCPHub is a centralized management and routing hub for builders…
MCPHub is an open-source centralized management and routing hub for connecting multiple MCP servers to AI clients, offering a unified dashboard, flexible routing, and access controls.
@omarsar0: If you build with MCPs, this one is worth reading. (bookmark it) The paper covers five recurring MCP server patterns ac…
This paper catalogues five recurring MCP server architectural patterns observed across fifteen independently developed servers, providing a taxonomy with context, problem, solution, and consequences. It also documents anti-patterns, cross-cutting concerns, and quantitative evaluations including inter-rater reliability and transport overhead.
@svpino: MCP is not dead. For the people who keep saying "bUt McP pUts GaRbaGe iN yOuR cOntExT", that's an outdated complaint: N…
A defense of MCP (Model Context Protocol) against criticism that it puts garbage in context, noting that modern tools like Claude Code, Codex, and Cursor implement progressive disclosure and load MCP tools on demand, making the complaint outdated. The author argues MCP is best for cloud-hosted platforms requiring authentication and discoverability.
Most MCP servers don't need to exist. Your case might be an exception
Most MCP servers are unnecessary; this article presents a framework for deciding when an MCP server is warranted, emphasizing the need for stable APIs and CLIs first.