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

[FEATURE]: Split MCP Servers from Docker MCP Toolki #6715

New Issue
Open
opened 2026-02-16 18:05:02 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:05:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @diegohb on GitHub (Jan 18, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Context

Assuming the default and standard configuration for MCP Server, the agent will load all tools and the TUI/GUI will show a single toggle on/off button.
Image

Problem

MCP Toolkit is designed to run at host and would presumably have multiple mcp servers configured and added used across different projects for various reasons.

Proposed

It would be ideal if it recognized this as an aggregation mcp server and parsed each mcp server instance coming from the feed as a separate MCP Server in TUI/GUI so end-users can toggle on/off the same way.

This can be made possible, or simpler, by asking users to configure their docker mcp toolkit as follows (one-time change):
docker mcp feature enable tool-name-prefix

This feature enables automatic prefixing of tool names with server names.
When enabled, all tools are automatically prefixed with their server name:

  • Example: 'search' becomes 'github:search'
  • Prevents name conflicts when multiple servers provide tools with the same name
  • Individual servers can override this with the 'prefix' field in their configuration

Workaround

Using tools configuration at global, where presumably you've configured Docker MCP Servers, disable all by default except primordial tools which agent can use to query for docker mcp servers dynamically.

{
	"$schema": "https://opencode.ai/config.json",
	"plugin": [
		"opencode-antigravity-auth@1.2.9-beta.3",
		"@mohak34/opencode-notifier@latest"
	],
	"tools": {
		"MCP_DOCKER*": false, //disable all
		"MCP_DOCKER_mcp-*": true // override to enable primordial functions
	},
	"mcp": {
		"MCP_DOCKER": {
			"type": "local",
			"command": [
				"docker",
				"mcp",
				"gateway",
				"run"
			],
			"enabled": true
		}
}

Then opt-in at project level configuration with overrides to enable (glob allowed):

{
  "tools": {
    "MCP_DOCKER_duckduckgo_*": true //override each mcp server with glob to include all its tools.
  }
}
Originally created by @diegohb on GitHub (Jan 18, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request ## Context Assuming the default and standard configuration for MCP Server, the agent will load all tools and the TUI/GUI will show a single toggle on/off button. <img width="1167" height="430" alt="Image" src="https://github.com/user-attachments/assets/d3e4fa7e-6dd1-428f-baad-e855d4070e94" /> ## Problem MCP Toolkit is designed to run at host and would presumably have multiple mcp servers configured and added used across different projects for various reasons. ## Proposed It would be ideal if it recognized this as an aggregation mcp server and parsed each mcp server instance coming from the feed as a separate MCP Server in TUI/GUI so end-users can toggle on/off the same way. This can be made possible, or simpler, by asking users to configure their docker mcp toolkit as follows (one-time change): `docker mcp feature enable tool-name-prefix` This feature enables automatic prefixing of tool names with server names. When enabled, all tools are automatically prefixed with their server name: - Example: 'search' becomes 'github:search' - Prevents name conflicts when multiple servers provide tools with the same name - Individual servers can override this with the 'prefix' field in their configuration ## Workaround Using tools configuration at global, where presumably you've configured Docker MCP Servers, disable all by default except _primordial tools_ which agent can use to [query for docker mcp servers dynamically](https://docs.docker.com/ai/mcp-catalog-and-toolkit/dynamic-mcp/). ```json { "$schema": "https://opencode.ai/config.json", "plugin": [ "opencode-antigravity-auth@1.2.9-beta.3", "@mohak34/opencode-notifier@latest" ], "tools": { "MCP_DOCKER*": false, //disable all "MCP_DOCKER_mcp-*": true // override to enable primordial functions }, "mcp": { "MCP_DOCKER": { "type": "local", "command": [ "docker", "mcp", "gateway", "run" ], "enabled": true } } ``` Then opt-in at project level configuration with overrides to enable (glob allowed): ```json { "tools": { "MCP_DOCKER_duckduckgo_*": true //override each mcp server with glob to include all its tools. } }
yindo added the discussion label 2026-02-16 18:05:02 -05:00
yindo commented 2026-02-16 18:05:02 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 18, 2026):

This issue might be a duplicate of or closely related to existing issues. Please check:

  • #514: Option to Enable / Disable MCP Servers (via TUI) - Core feature for toggling MCP servers via TUI interface, directly addressing the aggregation/split server UI problem
  • #5013: How to enable/disable mcp server per project - Per-project MCP server enable/disable functionality
  • #7482: dynamically registered MCP servers are not presented in TUI status - Addresses the issue of MCP servers from aggregation services not being properly displayed in TUI, similar to Docker MCP toolkit aggregation scenario
  • #7399: [FEATURE]: Filter which tools are loaded from MCP servers (includeTools/excludeTools) - Tool filtering that could work alongside server separation and prefixing
  • #8277: [FEATURE]: Lazy/dynamic loading for mcp tools - Dynamic loading of tools from multiple MCP servers, addressing context window concerns
  • #7466: [FEATURE]: Let LLM enable MCP on demand, default all MCPs off - Dynamic MCP enabling/disabling based on demand

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 18, 2026): This issue might be a duplicate of or closely related to existing issues. Please check: - #514: Option to Enable / Disable MCP Servers (via TUI) - Core feature for toggling MCP servers via TUI interface, directly addressing the aggregation/split server UI problem - #5013: How to enable/disable mcp server per project - Per-project MCP server enable/disable functionality - #7482: dynamically registered MCP servers are not presented in TUI status - Addresses the issue of MCP servers from aggregation services not being properly displayed in TUI, similar to Docker MCP toolkit aggregation scenario - #7399: [FEATURE]: Filter which tools are loaded from MCP servers (includeTools/excludeTools) - Tool filtering that could work alongside server separation and prefixing - #8277: [FEATURE]: Lazy/dynamic loading for mcp tools - Dynamic loading of tools from multiple MCP servers, addressing context window concerns - #7466: [FEATURE]: Let LLM enable MCP on demand, default all MCPs off - Dynamic MCP enabling/disabling based on demand Feel free to ignore if none of these address your specific case.
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 discussion
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#6715
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?