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

Open
opened 2026-02-16 18:05:49 -05:00 by yindo · 2 comments
Owner

Originally created by @tusxxx on GitHub (Jan 20, 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

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

Originally created by @tusxxx on GitHub (Jan 20, 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 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
yindo added the discussion label 2026-02-16 18:05:49 -05:00
Author
Owner

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

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

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

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

@github-actions[bot] commented on GitHub (Jan 20, 2026): This issue might be a duplicate of existing issues. Please check: - #9548: [FEATURE]: Add @ mention syntax for one-time MCP server activation in chat Feel free to ignore if none of these address your specific case.
Author
Owner

@Oronemu commented on GitHub (Jan 26, 2026):

I need this option too!

@Oronemu commented on GitHub (Jan 26, 2026): I need this option too!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6986