Add support for mcp-hub

[selmison]

Wouldn't it be a good approach add support for https://github.com/ravitemer/mcp-hub for manage MCP servers? In special to be able to add seamlessly of other MCP capabilities, as resource, prompt and so on...

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Feature Request: Tool to list and manage MCP servers to reduce context window #2418: Feature request for a tool to list and manage MCP servers to reduce context window usage
• Option to Enable / Disable MCP Servers (via TUI) #514: Request for option to enable/disable MCP servers via TUI to avoid context bloat
• Command to show available mcp servers #1899: Command to show available MCP servers (both detected and configured)

While your suggestion is specifically about integrating mcp-hub, these existing issues address similar MCP server management needs through built-in functionality. Feel free to ignore if mcp-hub offers specific advantages over these proposed solutions.

[rekram1-node]

Can't you already do that?

Never heard of it but at a glance it says it will hold all the mcp servers you want behind a single endpoint, why can't you just point opencode at your mcp hub url?

[selmison]

I believe that I can do this using plugins. Maybe I will try create this plugin later.

The idea is just a suggestion to use mcp-hub as builtin approach, as Avante, CodeCompanion and others do by using mcphub.nvim.

That way opencode could offload all details of implementation/maintenance of mcp client to single center point.

[rekram1-node]

Do you need a plugin tho?

Just add this to your opencode.jsonc:

{
....
 "mcp": {
    "mcp_hub": {
      "type": "remote",
      "url": "http://localhost:37373/mcp",
    },
  },

}

[rekram1-node]

MCP Hub acts as a central coordinator for MCP servers and clients, providing two key interfaces: Management Interface (/api/*): Manage multiple MCP servers through a unified REST API and web UI
MCP Server Interface (/mcp): Connect ANY MCP client to access ALL server capabilities through a single endpoint
This dual-interface approach means you can manage servers through the Hub's UI while MCP clients (Claude Desktop, Cline, etc.) only need to connect to one endpoint (localhost:37373/mcp) to access all capabilities. Implements MCP 2025-03-26 specification.

From their docs it says you just connect whatever client you want to the mcp hub through a single endpoint, opencode already supports this

[selmison]

MCP Hub acts as a central coordinator for MCP servers and clients, providing two key interfaces: Management Interface (/api/*): Manage multiple MCP servers through a unified REST API and web UI
MCP Server Interface (/mcp): Connect ANY MCP client to access ALL server capabilities through a single endpoint
This dual-interface approach means you can manage servers through the Hub's UI while MCP clients (Claude Desktop, Cline, etc.) only need to connect to one endpoint (localhost:37373/mcp) to access all capabilities. Implements MCP 2025-03-26 specification.

From their docs it says you just connect whatever client you want to the mcp hub through a single endpoint, opencode already supports this

It was clearer for me now. Make sense!! Thank you!!