Skip to content

[FEATURE]: Add @ mention syntax for one-time MCP server activation in chat #9696

Closed

Description

@tusxxx

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

Add the ability to temporarily enable MCP servers for a single request using @ mention syntax in the chat interface.

Current behavior:

Currently, MCP servers are either globally enabled or disabled in settings. To use an MCP server, users must:

Navigate to settings
Enable the desired MCP server
Send their request
Optionally go back to settings to disable it

This creates friction when users only need an MCP server for a specific one-off request.

Why it would be beneficial:

Convenience: Quickly invoke MCP tools without changing global settings
Efficiency: Reduces context switching between chat and settings
Clarity: Makes it explicit when MCP tools are being used in a conversation
Similarity to existing patterns: Mirrors the @ mention pattern used in many modern chat interfaces (Slack, Discord, etc.)

Suggested implementation:

Add @server_name syntax in chat to temporarily enable an MCP server for that request

Example: @github search for issues related to authentication
Example: @filesystem read the contents of config.json

The MCP server would only be active for that specific request
Show visual indication (e.g., badge or icon) that an MCP server was invoked
Support multiple @ mentions in a single request if multiple servers are needed
Add autocomplete suggestions when typing @ to show available MCP servers

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Jan 20, 2026
  2. github-actions commented on Jan 20, 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. Oronemu commented on Jan 26, 2026

    @Oronemu

    I need this option too!

  4. github-actions commented on Mar 29, 2026

    @github-actions
    Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

discussionUsed for feature requests, proposals, ideas, etc. Open discussion

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions