🎉 v4.10.0 - Support for MCP 2025-03-26 Spec!

[ravitemer]

Hi everyone!

MCP Hub joins very few MCP clients that support the latest MCP 2025-03-26 specification with dynamic OAuth registration and authorization, Streamble-HTTP as primary transport for remote MCP servers.

✨ What's New

Streamable HTTP: Primary protocol for remote servers (Auto fallback to SSE transport when server uses old spec)

• Auto-detection of transport (streamable-http/SSE)
• Auto OAuth authorization

OAuth Support

• Built-in OAuth with PKCE flow
• Better API key/token management

With these changes, all we need is the url of the MCP Server. No need to worry about API keys or security.

Example:

{
    "figma": { 
      "url": "https://figma.com/mcp"  //Not an actual server
    }
}

How this works?

MCP Hub first checks for server information stored at ~/.mcp-hub/oauth-storage.json. If it's available sets the Authorization header and starts the transport. If not available will show unauthorized status in the UI. Once the user press "l" on the server it will open a authorization url in the browser. Once the user authorizes the MCP Server for the app like gmail or github, it is redirected to MCP Hub where the code is exchanged for access_token and is then saved to ~/.mcp-hub/oauth-storage.json. Now the MCP Server connection is started with the new tokens. You only have to do this once. When the access_token expires MCP Hub refreshes it behind the scenes using the refresh_token.

OAuth and streamable-http makes it super easy and secure to configure MCP Servers. It also takes away the current headache regarding installing MCP Servers. Imagine gmail, github etc provide a https://gmail.com/mcp endpoint and that is all the users needs in his servers.json file. This makes discovering, installing MCP Servers easy and more secure 🚀

References

There are not many MCP Servers currently supporting streamable-http and oauth as this is very new in the spec. These might help MCP Server developers.

• Example Remote Servers: https://github.com/modelcontextprotocol/typescript-sdk/tree/main/src/examples/server

• Deploy Remote MCP Server with OAuth: https://developers.cloudflare.com/agents/guides/remote-mcp-server/
• Latest MCP Spec: https://modelcontextprotocol.io/specification/2025-03-26

✨ Features & Support Status

Category	Feature	Support	Details
Capabilities
	Tools	✅	Full support
	🔔 Tool List Changed	✅	Real-time updates
	Resources	✅	Full support
	🔔 Resource List Changed	✅	Real-time updates
	Resource Templates	✅	URI templates
	Prompts	✅	Full support
	🔔 Prompts List Changed	✅	Real-time updates
	Roots	❌	Not supported
	Sampling	❌	Not supported
MCP Server Transports
	Streamable-HTTP	✅	Primary transport protocol for remote servers
	SSE	✅	Fallback transport for remote servers
	STDIO	✅	For local servers
Authentication for remote servers
	OAuth	✅	With PKCE flow
	Headers	✅	For API keys/tokens
Chat Integration
	Avante.nvim	✅	Tools, resources, resourceTemplates, prompts(as slash_commands)
	CodeCompanion.nvim	✅	Tools, resources, resourceTemplates, prompts (as slash_commands)
	CopilotChat.nvim	✅	In-built support Draft
Marketplace
	Server Discovery	✅	Browse from verified MCP servers
	Installation	✅	Manual and auto install with AI
Advanced
	Smart File-watching	✅	Smart updates with config file watching
	Multi-instance	✅	All neovim instances stay in sync
	Shutdown-delay	✅	Can run as systemd service with configure delay before stopping the hub
	Lua Native MCP Servers	✅	Write once , use everywhere. Can write tools, resources, prompts directly in lua

🙌 Support

Any support to help maintain and improve the project by Sponsoring or ☕ Buying A Coffee will be greatly appreciated.