Devin
Add Edison Watch to Devin as a custom remote MCP server, in the cloud MCP Marketplace or the Devin CLI.
Devin (Cognition's autonomous AI software engineer) connects to Edison Watch as a custom remote MCP server. Devin exposes MCP configuration on two surfaces: Cloud Devin (app.devin.ai) lets an org admin add a custom MCP server under Settings > Connections, and the Devin CLI (Devin for Terminal) reads MCP servers from a .devin/config.json file. Both can point at Edison's public gateway.
Cloud Devin reaches your MCP server from Cognition's cloud, not from your laptop, so your connection URL must point at Edison's public gateway (https://mcp.edison.watch/...) - a localhost URL from the desktop app's local injection will not work. The CLI runs locally but should still use the gateway URL so its traffic is monitored.
1. Get Your Edison Connection URL
Your personal connection URL embeds your API key. For Devin, append ?client=devin so Edison tags the session as Devin in the dashboard:
https://mcp.edison.watch/mcp/<your-api-key>/?client=devinThe easiest way to get this URL is from the Edison Watch dashboard: open Settings, find the Api key / MCP URL section, click Get MCP URL, and pick Devin from the list - the dialog gives you a ready-to-copy URL with the ?client=devin tag already appended. (Alternatively, copy the base URL from the Edison Watch desktop app's Copy MCP URL menu and add ?client=devin yourself.) Treat this URL like a password - anyone with it can call MCP tools as you (subject to your Access Control Levels and policies).
The ?client=devin tag matters beyond the display label - Edison relies on it to recognize Devin and group its calls into the right session, so always include it.
The host differs per environment - release is mcp.edison.watch, and demo/self-hosted deployments use their own gateway host. Always copy the URL from your own desktop app rather than hardcoding the host.
2. Add Edison as a Custom MCP Server
How you add Edison - and whether each user's traffic is correctly attributed - differs sharply between the two surfaces. Read the attribution callout in each tab before choosing.
Cloud Devin's MCP servers are organization-shared, not per-user. Cognition's docs state that a custom MCP server is "shared within your organization" and that "all members' sessions use the same authenticated connection." Because every Edison connection URL embeds a personal, per-user API key, one org-wide Edison connector would authenticate and attribute every member's Devin activity to the single account whose key is in the URL - collapsing per-user monitoring, attribution, and policy enforcement into one identity. Cloud Devin has no per-user MCP option. If you need per-user attribution, use the Devin CLI tab instead.
Open Settings > Connections > Add a custom MCP (direct link: https://app.devin.ai/org/<your-org>/settings/connections/custom-mcp). The page is titled "Create a custom MCP server for your organization" and requires the Manage MCP Servers admin permission.
- Enter a Server name (e.g.
edison-watch); Devin auto-fills the Slug. Icon and Short description are optional. (You can instead click Import JSON to paste a server config.) - Under Connection, set Transport type to HTTP - Edison's gateway speaks streamable HTTP.
- Paste your full connection URL from step 1 into Server URL, including the trailing slash and
?client=devin. - Set Authentication to None. Edison authenticates via the API key in the URL - it has no OAuth sign-in and needs no separate header, so leave the Secrets section empty as well.
- Click Install and enable.
The Devin CLI (Devin for Terminal) is the documented path for per-user keys. A shared .devin/config.json (commit it to your repo) declares the server, and each developer supplies their own secret in a git-ignored .devin/config.local.json override - so every member's Edison traffic is attributed to them:
- In your repo's shared
.devin/config.json, declare anedisonMCP server withtype: "http"and the gateway URL (without the key, if you reference the key via a variable). - Each member adds their own
?client=devinconnection URL (or its API-key portion) to their personal.devin/config.local.json, which is git-ignored and never shared. - Distribute the Edison Watch desktop app so each member can copy their own connection URL from step 1.
See Cognition's CLI MCP configuration docs for the exact config schema. This keeps every member's traffic correctly attributed to them in the Edison dashboard, where admins get org-wide visibility across all of them.
Adding org-level custom MCP servers in Cloud Devin requires the Manage MCP Servers permission, which in practice lives in Devin's admin/role controls (Teams and Enterprise). Cognition's pricing page does not name MCP per plan, so confirm availability on your plan before rolling Edison out.