Cloud Agent run cannot see enabled Team MCP servers (Server "notion" not found)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

We’re seeing a mismatch between the Cursor UI and the actual Cloud Agent runtime.

Team-side setup appears correct:

Team MCP server Notion is configured as an HTTP server at mcp.notion.com/mcp.
In cursor dot com/agents, the Notion MCP toggle is enabled for the run and shows as connected rather than Login.
The workspace also contains a matching MCP config for notion at the same endpoint, plus a Prisma MCP entry.mcp.json:1-12
However, inside the Cloud Agent run, no MCP servers are exposed:

ListMcpResources() returns no resources.
ListMcpResources(server: “notion”) returns Server “notion” not found.
ListMcpResources(server: “Prisma”) also returns Server “Prisma” not found.
This suggests the issue is not Notion auth/config itself, but that the Cloud Agent runtime is not receiving any enabled MCP servers from the backend for this run.

Runtime context:

This is a Cloud Agent VM using the backend exec-daemon harness, not a local Cursor desktop app.
There is no local cursor binary in the VM; only the cloud execution daemon is present.cursor_env_check.txt:1-7

Steps to Reproduce

In Team Settings → Integrations & MCP, configure a Team MCP server named Notion as an HTTP MCP pointing to mcp dot notion dot com/mcp, with the required auth header. The workspace also contains a matching notion MCP entry, plus a Prisma MCP entry, so the expected server names are notion and Prisma.mcp.json:1-12
Open cursor dot com/agents, start a new Cloud Agent run for the repo, and enable the Notion MCP from the MCP dropdown.
Confirm the MCP appears connected in the UI (toggle enabled, no Login prompt).
In the running Cloud Agent session, ask the agent to enumerate MCP servers/resources.
Observe that the runtime returns no MCP resources.
Then ask the agent to target the configured server directly, for example by checking notion.
Observe that the runtime reports Server “notion” not found.
Repeat the same check for another configured MCP server such as Prisma.
Observe that it also reports Server “Prisma” not found, suggesting the issue is that no MCP servers are being attached to the Cloud Agent runtime, not that the Notion config itself is invalid.
Optional extra evidence: inside the VM, only the cloud execution daemon is present, not a local Cursor desktop app, which suggests this is a backend/runtime attachment issue for Cloud Agents rather than a local app state issue.cursor_env_check.txt:1-7

Expected Behavior

If Team MCP Notion is enabled and connected in cursor dot com/agents, the Cloud Agent should be able to enumerate and use that MCP server during the run.

Actual behavior
The UI shows the MCP as enabled/connected, but the agent runtime reports that the server does not exist.

Screenshots / Screen Recordings

Screenshot 2026-04-07 at 4.24.10 PM.png
Screenshot 2026-04-07 at 4.24.10 PM.png2552×1704 242 KB

Operating System

MacOS

Version Information

cursor dot com / agents (cloud agent)

For AI issues: which model did you use?

GPT-5.4 High

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hi there,

Thanks for the detailed write-up and diagnostic steps — this is a known issue affecting MCP servers in Cloud Agent runs. The UI correctly shows the MCP as enabled/connected, but the cloud agent runtime fails to attach the configured servers. You’re not the only one hitting this — other users have reported the same behavior in this thread and this one.

Two things worth noting:

  1. The workspace mcp.json (where your Prisma entry lives) is not read by the cloud agent runtime. Cloud agents only pick up MCP servers configured through the dashboard (Team Settings > Integrations & MCP), not from repo-level config files. So Prisma is expected to be unavailable.

  2. Team/user dashboard-configured HTTP MCP servers (like your Notion setup) should work but currently have reliability issues in the cloud agent pipeline. Our team is actively investigating this.

Unfortunately there’s no workaround for the Notion MCP in cloud agents right now. I’ve flagged this thread with the engineering team to help prioritize the fix. In the meantime, MCP servers work reliably in local Cursor desktop agent sessions if that’s an option for your workflow.

8

Understood. With the push to make the cloud agent experience more primary for AI factories, I’d love to see this be addressed soon, as it is pretty critical for our workflows.

Note: I believe this does work on individual accounts, but not for teams.

9

@mohitjain any update here?

10

Thanks for following up. Unfortunately, I don’t have a concrete update yet – the issue is still being tracked and prioritized by the engineering team, but a fix hasn’t shipped.

I know this is critical for your workflow, especially with the push toward cloud agents as a primary experience. I’ll flag this again internally to help move it forward.

1 Like
11

Just to double flag it, I am encountering the same issue, and would be very happy about a fix. Thanks cursor team!

1 Like