Feature Request: Limiting number of MCP tools based on configuration

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.

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

Enable/Disable MCP server by Mode #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
Feature Request: Add MCP to modes config #852: Feature Request: Add MCP to modes config - similar request for tool permissions and context management for different modes using different sets of MCPs
A Command to List Tools #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.

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

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

@rekram1-node

@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

@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

Navigation Menu

Repository navigation

Feature Request: Limiting number of MCP tools based on configuration #2172

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Feature Request: Limiting number of MCP tools based on configuration #2172

Description

Activity

github-actions commented on Aug 22, 2025

rekram1-node commented on Aug 22, 2025

rekram1-node commented on Aug 22, 2025

robhittme commented on Aug 22, 2025

rekram1-node commented on Aug 22, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions