You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Add @ mention syntax for one-time MCP server activation in chat #9696
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
github-actions commentedon Jan 20, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
Oronemu commentedon Jan 26, 2026
I need this option too!
github-actions commentedon Mar 29, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.