Local agent cannot access user MCP servers from mcp.json (Auth0, Datadog, Snowflake stripped; only plugin MCPs exposed)

Support Help
1

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

Local agent sessions cannot use user-configured MCP servers from ~/.cursor/mcp.json, even when those servers show as connected in Cursor Settings → MCP. Only plugin MCPs (Datadog, Notion, Slack, Vercel) are forwarded to the agent tool bridge. This breaks Auth0, Datadog (user config), Snowflake, Observe, and other custom MCPs.

Steps to Reproduce

  1. Configure multiple user MCP servers in ~/.cursor/mcp.json (e.g. Auth0, Datadog, Snowflake).
  2. Verify they show connected with tools in Cursor Settings → MCP.
  3. Start a local agent chat and ask the agent to use one of those MCPs (e.g. “search Datadog logs” or “list Auth0 users”).
  4. Agent calls mcp_get_tools — only plugin servers appear.

Expected Behavior

Agent should have access to the same MCP servers the user has enabled and connected in Settings, including stdio/HTTP servers from mcp.json.

Operating System

MacOS

Version Information

  • OS: macOS (darwin 25.5.0), arm64
  • Cursor Version: 3.9.16 (stable)
    Cursor Agent
    v2026.07.01-41b2de7

For AI issues: which model did you use?

composer 2.5

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hey there,

This is a known limitation right now: agents you run or control from the iOS app use the MCP servers configured for Cloud Agents, not the ones in your desktop’s local ~/.cursor/mcp.json. That’s why only the marketplace/plugin servers (Datadog, Notion, Slack, Vercel) come through. The “connected” state you see in desktop Settings → MCP reflects your local desktop’s MCP client, which is separate from what a mobile or remote-controlled agent can reach.

To make Auth0, Snowflake, Datadog, etc. available to mobile/remote agents, add them via the MCP dropdown at cursor.com/agents, then pick which ones a run uses when you launch it in the app. Both HTTP and stdio transports are supported there. One caveat: the server runs in the agent’s cloud environment, so anything that points at a local-only resource on your Mac needs to be reachable over the network.

This is an area we’re actively improving for mobile and remote-controlled agents. More detail here: Cloud Agent MCP support.

Let me know if that gets your servers showing up!