Cursor as an MCP client

Discussion
1

would love to see official MCP client support in cursor, just like the claude desktop app.

MCP so far looks like an promising standard to bring data and tools to LLMs. There’s also an growing ecosystem of MCP servers doing all sorts of things https://github.com/punkpeye/awesome-mcp-servers

If Cursor can be an MCP client, we can build and share custom MCP servers to automate even more software dev work directly inside Cursor.

Reference Servers built by MCP team: https://github.com/modelcontextprotocol/servers

This would allow us to do things like query postgres databases, interact with Cloudflare/Github APIs, search arxiv, read apple/obsidian notes, and a lot more directly within the chat window.

I’m already building custom MCP servers to use with the Claude app because its so easy to generate and control.

Anyways, im curious about what everyone thinks about this idea. Are you guys playing with MCP?

2 Likes
2

Hey, I’m impressed by this too, and I’d also like to have it in Cursor. Maybe it will appear soon.

1 Like
3

+1.
There’s new MCP tools being added daily, and I’ve found them quite useful in Claude Desktop.

2 Likes
4

Bump

Could you imagine the potential for the user and the model to be able to collaborate on quickly generating little tools, with direct access to the state of the editor/filesystem/docs/debugger/etc? Unlimited

3 Likes
5

bump.

This is a really good add to the cursor product.

1 Like
6

Hey, we plan to implement this, but I can’t say when it will be yet.

3 Likes
7

awesome to hear that @deanrie looking forward to it!

8

Absolute must - integrate it with composer and its game over.

9

While I can’t guarantee it will come to the Cursor client, we are testing MCP internally to see what’s possible and how it might fit in the workflow of Cursor.

1 Like
10

I’ve been writing MCP Servers for the last few weeks. It’s a game changer. It’s definitely for more advance usage, but it could be a way cursor itself add/enable extensions to itself for composer.

1 Like
11

I actually use Claude Desktop way more with MCP. :grimacing::ok_hand:

image
image250×112 4.68 KB

It’s true that MCP tools could eventually substitute for some current Cursor functionality, but that’s coming regardless, and MCP support could also improve Cursor’s capabilities by leveraging community made tools, or creating it’s own (as mentioned above.)

Cline already does this:

“add a tool that…”

Thanks to the Model Context Protocol, Cline can extend his capabilities through custom tools. While you can use community-made servers, Cline can instead create and install tools tailored to your specific workflow. Just ask Cline to “add a tool” and he will handle everything, from creating a new MCP server to installing it into the extension. These custom tools then become part of Cline’s toolkit, ready to use in future tasks.

  • “add a tool that fetches Jira tickets”: Retrieve ticket ACs and put Cline to work
  • “add a tool that manages AWS EC2s”: Check server metrics and scale instances up or down
  • “add a tool that pulls the latest PagerDuty incidents”: Fetch details and ask Cline to fix bugs

I’m pretty confident the Cursor team can keep finding new ways of ‘staying ahead’, but overlooking MCP seems like a sure way to fall behind…