Where does the bug appear (feature/product)?
Background Agent (GitHub, Slack, Web, Linear)
Describe the Bug
In our organization, when working on your local cursor instance, we use rules to define how to agent should investigate a certain task or validate the written code using different mcps.
currently, we’re using playwright, atlassian, lsmcp, and gcp to cover the entire flow we defined in our rules.
we recently activated background agents and I noticed that on the background agents, none of our mcps are available so the agent can’t follow our developer rules.
as a temporary solution, we have rules we include intelligently for background agents to skip some of those validations, but in an ideal world, I would much prefer if tasks we launch in the background will be able to work the same as when we’re working against the agent ourselves.
is there a way to make it work that I just didn’t find yet? is it a planned feature? if so, any idea how long until it will be available?
and for the community, did anyone had this problem as well? do you have an unofficial solution to launch tasks in the background WITH access to extra tools?
thanks!
Steps to Reproduce
add an mcp to the repo’s mcp.json and run a background agent that should call the added mcp.
Expected Behavior
expected: the agent should do a tool call through the mcp even on a background agent
actual: agent doesn’t call the tool and says the tool is unavailable
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.4.5
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
Does this stop you from using Cursor
No - Cursor works, but with this issue
