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 Request: Limiting number of MCP tools based on configuration #1442

New Issue
Closed
opened 2026-02-16 17:30:59 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 17:30:59 -05:00
Owner
Copy Link
Copy Source

Originally created by @robhittme on GitHub (Aug 22, 2025).

Originally assigned to: @thdxr on GitHub.

This would be more of a "nice to have". Currently using the docker mcp toolkit which makes it easy to configure multiple mcp servers. However there is no way to limit the tools being used by each of the mcp servers. For example the Github Official has 85 tools in total. Most of the time models will breakdown after 40. In cursor they have made it so you can select which tools you want to be accessible.

It would be great to have a similar feature so i can choose which tools I want to utilize in the configuration.

Originally created by @robhittme on GitHub (Aug 22, 2025). Originally assigned to: @thdxr on GitHub. This would be more of a "nice to have". Currently using the docker mcp toolkit which makes it easy to configure multiple mcp servers. However there is no way to limit the tools being used by each of the mcp servers. For example the Github Official has 85 tools in total. Most of the time models will breakdown after 40. In cursor they have made it so you can select which tools you want to be accessible. It would be great to have a similar feature so i can choose which tools I want to utilize in the configuration.
yindo closed this issue 2026-02-16 17:30:59 -05:00
yindo commented 2026-02-16 17:30:59 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Aug 22, 2025):

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

  • #1101: Enable/Disable MCP server by Mode - requests ability to limit MCP tools available to specific modes with granular control over which tools are enabled
  • #852: Feature Request: Add MCP to modes config - similar request for tool permissions and context management for different modes using different sets of MCPs
  • #1142: A Command to List Tools - requests ability to list and manage tools, toggle tools for specific sessions

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

@github-actions[bot] commented on GitHub (Aug 22, 2025): This issue might be a duplicate of existing issues. Please check: - #1101: Enable/Disable MCP server by Mode - requests ability to limit MCP tools available to specific modes with granular control over which tools are enabled - #852: Feature Request: Add MCP to modes config - similar request for tool permissions and context management for different modes using different sets of MCPs - #1142: A Command to List Tools - requests ability to list and manage tools, toggle tools for specific sessions Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:30:59 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 22, 2025):

Technically you can do this by disabling tools, example with context7:

"tools": {
  "context7*": false
}

^^ that disables all context7 tools, you can also disable a particular tool like:

"tools": {
  "context7_resolve_library_id": false
}

How would setting a # of tools to show work? seems like it'd be really arbitrary if we tried to handle which ones for you...

@rekram1-node commented on GitHub (Aug 22, 2025): Technically you can do this by disabling tools, example with context7: ``` "tools": { "context7*": false } ``` ^^ that disables all context7 tools, you can also disable a particular tool like: ``` "tools": { "context7_resolve_library_id": false } ``` How would setting a # of tools to show work? seems like it'd be really arbitrary if we tried to handle which ones for you...
yindo commented 2026-02-16 17:30:59 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 22, 2025):

Also I would warn against using 80+ mcp tools I think your model performance will degrade

@rekram1-node commented on GitHub (Aug 22, 2025): Also I would warn against using 80+ mcp tools I think your model performance will degrade
yindo commented 2026-02-16 17:30:59 -05:00
Author
Owner
Copy Link
Copy Source

@robhittme commented on GitHub (Aug 22, 2025):

@rekram1-node agreed with limiting mcp tools. I generally only want to use a few tools from each mcp server, but unable to specify which tool from each mcp server I want, which leads to all the tools being loaded.

Ideally there would be a whitelist of the tools you would like to use. Default to all if not specified otherwise.
maybe something like this

"jira-mcp": {
      "type": "local",
      "command": [
        "docker",
        "mcp",
        "gateway",
        "run"
      ],
      "enabled": true,
      "allowedTools": [
        "jira_create_issue",
        "jira_search",
        "jira_get_issue",
        "jira_update_issue",
        "confluence_search",
        "confluence_get_page"
      ]
    }
@robhittme commented on GitHub (Aug 22, 2025): @rekram1-node agreed with limiting mcp tools. I generally only want to use a few tools from each mcp server, but unable to specify which tool from each mcp server I want, which leads to all the tools being loaded. Ideally there would be a whitelist of the tools you would like to use. Default to all if not specified otherwise. maybe something like this ``` "jira-mcp": { "type": "local", "command": [ "docker", "mcp", "gateway", "run" ], "enabled": true, "allowedTools": [ "jira_create_issue", "jira_search", "jira_get_issue", "jira_update_issue", "confluence_search", "confluence_get_page" ] } ```
yindo commented 2026-02-16 17:30:59 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 22, 2025):

@robhittme but you can already do this?

"tools": {
    "context7*": false,
    "context7_resolve_library_id": true
  }

This will disable all context7 tools by default but explicitly allows context7_resolve_library_id

@rekram1-node commented on GitHub (Aug 22, 2025): @robhittme but you can already do this? ``` "tools": { "context7*": false, "context7_resolve_library_id": true } ``` This will disable all context7 tools by default but explicitly allows `context7_resolve_library_id`
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#1442
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?