Skip to content

[FEATURE]: Let LLM enable MCP on demand, default all MCPs off #7466

Closed as not planned

Description

@imqqmi

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

MCPs can increase the agent prompt significantly while oftentimes they're not even used in all sessions. Similar to skills, add (generate?) short descriptions of the MCPs and let the LLM enable them for the current session so that disabled MCPs can be activated on demand. Custom agent prompts by users and skills can also instruct the LLM to enable and use a certain MCP when the situation calls for it.

ie:

  • a user tasks the LLM to create unit tests for laravel 12 using pest.
  • LLM doesn't know pest so it creates an older version of PHPUnit compatible tests
  • Deprecation warnings ensue
  • User prompts to fix the deprecation issues with context7, but it's as yet disabled.
  • LLM enables context7, reads the instructions from the MCP and queries it for PHPUnit to Pest migration instructions
  • LLM fixes issues and the tests are now best practice compliant.

This way, having a large set of MCP servers doesn't give you the penalty of a overly large system prompt, saving costly tokens and making more efficient use of the context so that the LLM doesn't get confused, improving the general coding experience and code quality.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Jan 9, 2026
  2. github-actions commented on Jan 9, 2026

    @github-actions
    Contributor

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

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

  3. imqqmi commented on Jan 9, 2026

    @imqqmi
    Author

    It's the same as #7406, though in my issue, the description is in the issue itself, not a link to a reddit post.

  4. thdxr commented on Mar 25, 2026

    @thdxr
    Member

    To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

  5. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on May 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions