Explicit MCP Server Selection with “@” Command

Feature Requests
1

Overview

Currently, when specifying MCP servers in prompts, Cursor sometimes does not adhere to the intended selection, leading to inconsistencies in behavior. To resolve this, I propose the introduction of an explicit @ command that allows users to directly designate which MCP server to use in both Chat and Composer modes.

Feature Description

The proposed feature would implement a simple syntax—using the @ command (e.g., @mcp serverName)—that users can include in their prompt. This command would act as a high-priority directive, ensuring that Cursor unambiguously utilizes the specified MCP server, overriding any ambiguous or conflicting context from the rest of the prompt.

Benefits

• Precision & Control: Users can enforce a specific MCP server, reducing misinterpretations and ensuring consistent behavior across sessions.

• Enhanced Developer Experience: Direct control over server selection will help avoid unexpected outcomes, leading to smoother and more reliable workflows.

• Seamless Integration: The command would be uniformly recognized in both Chat and Composer, simplifying usage and reducing the need for additional configuration.

1 Like
2

Mayhaps keep a sqlite/postgress/csv of all your MCPs with the invokation and other meta and have a metho to call from such any MCP - and also you could have the narrative description of the MCPs function to say "give me the [such_and_such MCP for piping/getting blah]

You get the idea…

Abstract the MCP calls such that youre pulling them from your source of truth.

and for public MCPs, give people a gist with the table, mcp call, code. for little tools.

with a qrcode for the gist. haha

3

We are hoping to add MCP tools to the @ menu soon, but have some improvements to make first before this is feasible!

1 Like
4

Sounds awesome. I look forward to the release.

5

Yea this sounds awesome!