anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Add support for mcp-hub #1639

New Issue
Closed
opened 2026-02-16 17:31:54 -05:00 by yindo · 7 comments
yindo commented 2026-02-16 17:31:54 -05:00
Owner
Copy Link
Copy Source

Originally created by @selmison on GitHub (Sep 6, 2025).

Originally assigned to: @thdxr on GitHub.

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...

Originally created by @selmison on GitHub (Sep 6, 2025). Originally assigned to: @thdxr on GitHub. 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...
yindo closed this issue 2026-02-16 17:31:54 -05:00
yindo commented 2026-02-16 17:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Sep 6, 2025):

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

  • #2418: Feature request for a tool to list and manage MCP servers to reduce context window usage
  • #514: Request for option to enable/disable MCP servers via TUI to avoid context bloat
  • #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.

@github-actions[bot] commented on GitHub (Sep 6, 2025): This issue might be a duplicate of existing issues. Please check: - #2418: Feature request for a tool to list and manage MCP servers to reduce context window usage - #514: Request for option to enable/disable MCP servers via TUI to avoid context bloat - #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.
yindo commented 2026-02-16 17:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Sep 6, 2025):

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?

@rekram1-node commented on GitHub (Sep 6, 2025): 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?
yindo commented 2026-02-16 17:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@selmison commented on GitHub (Sep 6, 2025):

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.

@selmison commented on GitHub (Sep 6, 2025): 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](https://ravitemer.github.io/mcphub.nvim/extensions/avante.html), [CodeCompanion](https://ravitemer.github.io/mcphub.nvim/extensions/codecompanion.html) and others do by using [mcphub.nvim](https://ravitemer.github.io/mcphub.nvim/). That way `opencode` could offload all details of implementation/maintenance of mcp client to single center point.
yindo commented 2026-02-16 17:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Sep 6, 2025):

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 commented on GitHub (Sep 6, 2025): Do you need a plugin tho? Just add this to your opencode.jsonc: ``` { .... "mcp": { "mcp_hub": { "type": "remote", "url": "http://localhost:37373/mcp", }, }, } ```
yindo commented 2026-02-16 17:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Sep 6, 2025):

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

@rekram1-node commented on GitHub (Sep 6, 2025): > 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](https://modelcontextprotocol.io/specification/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
yindo commented 2026-02-16 17:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@selmison commented on GitHub (Sep 6, 2025):

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!!

@selmison commented on GitHub (Sep 6, 2025): > > 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](https://modelcontextprotocol.io/specification/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!!
yindo commented 2026-02-16 17:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@DanRioDev commented on GitHub (Oct 21, 2025):

Yet @selmison , it does not support MCPHub's native servers

@DanRioDev commented on GitHub (Oct 21, 2025): Yet @selmison , it does not support MCPHub's native servers
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1639
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?