Cloud Agents + MCP

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Cloud agents cannot use MCPs, even though I was told by support that this feature is now available: gist:de77afcf288b128a62b56be12698e40b · GitHub.

Steps to Reproduce

Start a cloud agent in the repo attached: gist:bae06bedf0911f6bdf8e0efd0c6106bc · GitHub.

Expected Behavior

It should be able to use the MCP tools

Operating System

Linux

Version Information

Cloud Agents

For AI issues: which model did you use?

Claude Opus 4.6

For AI issues: add Request ID with privacy disabled

bc-bf6412c8-324b-43ca-80ae-f88e5fa92c34

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey there!

We’re quite close on this one, but it’s not GA yet. Sorry for the mix-up.

4 Likes
4

Can you chime in here when it is released to GA?

5

Same issue here. We need Cloud Agents from Slack to create documents in Outline via MCP.

Is there a way to configure MCP for Cloud Agents at team level? Or any workaround? Our use case: sales team creates offers via @Cursor in Slack — we need direct publication to Outline, not just local file.

6

Same, I’m a bit shocked that cloud agents have been around this long and don’t have MCP. Codegen (already acquired), EngineLabs, what not already supported it

8

Please let us know when this is live! I’m sure you have hundreds of user looking to control their codebase via Slack and without DB/MCP access cloud agents are largely futile cause they lack data context

9

Does the Feb 24, 2026 release now enable Cloud Agents to use custom MCP servers? Please explain where in the Cursor Cloud Agent API an MCP configuration can be supplied in the launch payload. I don’t see a way to configure a custom MCP server for Cloud Agents via the Cursor Dashboard.

Per Cloud Agents API | Cursor Docs , it says “MCP (Model Context Protocol) is not yet supported by the Cloud Agents API.” When will it be supported because Capabilities | Cursor Docs implies that custom MCP servers are now supported.

11

Hey there @banool @svinuh @bholagabbar @Justin_Wickett

  1. You can find MCP Servers for Cloud Agents now on http://cursor.com/agents :slight_smile: A bigger launch is coming this week, but we’d love for you to try it out already!

  2. Cloud Agents created via the API should still be able to call MCPs, as long as you’ve enabled the MCPs for that repo via the Agents dashboard.

2 Likes
13

Colin, will Custom MCP servers be configurable programmatically on an Cloud Agent-by-Cloud Agent basis? Meaning is there an API endpoint to launch a Cloud Agent with a custom MCP server attached to it rather than manually having to manually define Custom MCP Server details at the Dashboard level?

14

MCP (Model Context Protocol) is not yet supported by the Cloud Agents API.

1 Like
15

Thanks! I was able to configure Linear and Supabase. A bit confused as to how these work per repo. Am I able to configure MCPs per repository ? When I initiate a cloud agent from slack for example, do I tell it to use certain MCPs or will they always have access ?

16

Cloud agents, including those triggered by a Slack command, will automatically pick up MCP servers defined in .cursor/mcp.json in your repo.

Read below!

18

@Colin

This behaviour is not working for me. Cloud Agents do not pick up my .cursor/mcp.json file and start up the MCP processes in the background.

Here is a thread demonstrating the behaviour: https://cursor.com/agents/bc-75e5954a-1210-4e3e-923c-7180402b3f28

Here is the mcp.json file

{

  "mcpServers": {

"notionApi": {

"command": "bash",

"args": ["scripts/run-notion-mcp.sh"]

    }

  }

}

Here is the MCP startup script

#!/usr/bin/env bash

set -e

ROOT="$(cd "$(dirname "$0")/.." && pwd)"

cd "$ROOT"

if [ -f .env ]; then

echo "Running Notion MCP with .env file"

exec npx -y dotenv-cli -e .env -- npx -y @notionhq/notion-mcp-server "$@"

else

echo "Running Notion MCP without .env file"

exec npx -y @notionhq/notion-mcp-server "$@"

fi
1 Like
19

I’m not seeing this behavior. For example: https://cursor.com/agents/bc-58dff791-4b03-416a-987d-86c16c2a583c

Here’s my .cursor/mcp.json file:

{
    "mcpServers": {
        "laravel-boost": {
            "command": "php",
            "args": [
                "artisan",
                "boost:mcp"
            ]
        },
        "smartbear": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@smartbear/mcp@latest"
            ],
            "env": {
                "BUGSNAG_AUTH_TOKEN": "${env:BUGSNAG_AUTH_TOKEN}",
                "BUGSNAG_PROJECT_API_KEY": "${env:BUGSNAG_PROJECT_API_KEY}"
            }
        }
    }
}

And if I create the mcp at cursor.com/agents, there is no way that I have been able to figure out for the smartbear one to pick up those env secrets. If I use the cloud agent terminal, I can echo them, so they’re on the VM, but the MCP has no ability to see them. I’ve tried with no env block in the mcp config, the ${env:} interpolation thing, and putting the actual key / value secrets into the custom MCP setup at cursor.com/agents. In every case, the SmartBear tool says it can’t find the auth token and API key. Works fine locally in Cursor.

Please help! Cloud Agents are relatively useless to me if you can’t interact with any external services except the handful in the marketplace…

1 Like
20

Thanks, everyone. It looks like some bad information got into our Help Center (I’m opening a PR to fix this now).

The supported way to add MCP Servers for Cloud Agents is to configure them via the dashboard:

  • https://cursor.com/agents
  • For users on a Team Plan: https://cursor.com/dashboard/integrations

@Robin_Weston For you, that should just mean configuring a custom MCP server:

Screenshot 2026-03-17 at 17.08.01
Screenshot 2026-03-17 at 17.08.011600×1034 165 KB

@ryanw I can confirm that configuration interpolation isn’t working for MCP Servers configured for Cloud Agents. When configuring the MCP, you’ll need to use the actual secret value.

I set up a SmartBear account to verify, and everything is working for me with this configuration:

Screenshot 2026-03-17 at 17.53.38
Screenshot 2026-03-17 at 17.53.38920×690 19.1 KB

{
  "mcpServers": {
    "smartbear": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BUGSNAG_AUTH_TOKEN": "TOKEN",
        "BUGSNAG_PROJECT_API_KEY": "KEY"
      }
    }
  }
}

(Replace TOKEN and KEY with their actual values.)

Screenshot 2026-03-17 at 17.52.01
Screenshot 2026-03-17 at 17.52.012282×726 49.3 KB

Can you try reconfiguring your SmartBear MCP in the portal with the actual secret values (which are still encrypted in the database) hardcoded in the env field (not using ${env:...} interpolation), and let me know if that works for you?

I’ll file a report with the team about the config interpolation!

22

Thanks for the update. Configuring via the dashboard works.

Can you please consider establishing a single source of truth for MCP config across local and agents? Having duplicated definitions across two mcp.json files means they may well drift apart over time, and it adds friction to the “it just works” process of firing up a Cloud agent.

Thanks,

Robin

Restricted
2 Likes
23

Unfortunately, it’s still not working for me, even if I edit the mcp json (on cursor.com/agents) and put the token and key directly into the json. Agent always says the same thing:

" BugSnag MCP tools are available but not configured. Both calls returned:

“The tool is not configured - configuration options for BugSnag are missing or invalid.”

I’ve double-checked that my keys and values are the same in local (where this works fine) as cloud…could this possibly be related to whitelisting domains?

24

Any update on this? Now cloud agents can’t see this MCP server at all :frowning: