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:
-
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. -
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.