Can MiniMCP (a lightweight stateless MCP server framework) be part of the SDK?

[sreenaths]

Question

I’ve built a lightweight MCP server framework called MiniMCP on top of the MCP Python SDK.

MiniMCP was created mainly for remote MCP servers. It rethinks the server implementation to focus on simplicity, stateless message handling, and transport-agnostic design. It provides a single async handler function for processing MCP messages, making it easy to embed in frameworks like FastAPI.

My question is: Can MiniMCP be contributed to the official SDK? If not, can it be contributed to the modelcontextprotocol community as a companion project?

Additional Context

Key features include:

• Stateless, scalable, and transport-agnostic core
• Simple async handler for JSON-RPC 2.0 messages
• Built-in transports (stdio, HTTP, and Smart Streamable HTTP)
• Easy integration with frameworks such as FastAPI
• Typed scope/context for passing auth/session/db info
• Lightweight (depends only on official MCP SDK)

[Kludex]

Link?

[sreenaths]

Hi @Kludex

Sorry that I missed your message from Oct 3rd.
I had originally added the link, but had to remove it for further improvements.

For reference, here’s the MiniMCP PR: #1761

\cc @felixweinberger