Cursor Background agent doesn't call MCP?


I’m using the beta version of the Cursor background agent.
When I open a new window for the background agent, I can access the MCP settings and add the required MCP servers, but they don’t work.
I’d like to know whether this feature isn’t supported yet or if the issue is specific to me.
I’d also like to know if MCP support is planned for the background agent in the future.

If anyone has it working, please let me know how you got it to run.

Ignore that ai’s respond. Because when i call that mcp not in the background agent, it works appropriately.

3 Likes

Hi, while we wait for Cursor team to reply, did you setup the MCP inside the Backround Agent or is it an SSE public URL MCP?

i apply .cursor/mcp.json in my project folder and commit & push. so when i open the background agent, it comes out because this mcp.json file is in my git. but when i opened at first, this mcp doesn’t activate so i activate with toggle button.

image

Any updates ?

3 Likes

I am also waiting for the update. I can use multiple MCP in foreground but not get success yet in background agent

This is such a core feature for me. I want to be able to spin off background agents while on the go from my phone, and I want it to be able to access Supabase via the MCP. Please, Cursor team, add support for this!

1 Like

Whats going on here this has been an ask for months now. Cloud agents aren’t very useable without supplemental context

For anyone else facing this issue I found a work around for local mcps. I ended up making a cli wrapper that reads a .cursor/mcp.json and allows the agent to call local mcps through the command line. Isn’t pretty but has worked well enough

setting up and calling mcp from within background agents would be an absolute game changer for us. just imagine using cursor to create comments or update stories in the product management tool.

Is there “already” a feature request for this?