Background Agent MCP Access

Feature Requests
1

The Background Agent always has MCP disabled, even though they are configured in the project. My use-case:
Sentry errors come to me via slack, and the Sentry AI writes very nice summaries of the issue by watching replays and looking through all the logs. I can only access the output of the Sentry AI via the Sentry MCP. The analysis from the Sentry AI is enough information for a Background Agent to do a very good job at resolving the issue, but the background agent doesn’t start with the MCP enabled. I can open the agent, go to settings, and turn it on and it will work.

If it started with the MCP enabled, then I could trigger the background agent from Slack, inline with the sentry issue notification. It could all run nicely in the background and be ready for me to review when done.

2 Likes
2

Did you figure this out? In the Background Agent VM I can see my servers but they’re disabled. Tried quite a few things to enable them but nothing has worked so far

3

Hey all - working on this!

2 Likes
4

wow, did not expect a reply. Very excited. I will stop trying to hack the SQLite DB to enable those switches. Looking forward to this feature

5

Do you have any news on this? If you store mcp.json file in .cursor, the agent recognizes it should have access to the mcp but the authentication doesn’t work. I have the exact same Sentry AI use case as mentioned here.

1 Like