I’ve been playing around with the new MCP Server functionality and adding tools to my Composer Agent, and it’s working great.
But I’ve quickly discovered that the current way we define MCP Server is global, and I have some MCP Server tools that are project specific. It would be great to be able to manage these at a global vs project level so the context of the composer agent never gets confused by project specific tools that should not exist in their context.
That’s all, thanks!
This will be a really nice feature, to be able to store MCP config inside the project, and use env variables there. So other people who checkout from git can easily configure MCP servers by providing necessary variables.
Totally agreed. I had not even thought about MCP config inside of the project repo but totally makes sense. I’m sure that there are really powerful global MCP tool use applications as well but most of the value I’m finding it current is project specific.
This is awesome.
As of 0.46:
Configure Project Servers with `/.cursor/mcp.json
We have a solution for this now! Thanks Cursor devs.