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:
@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:
{
"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.)
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!