Skip to content

Connect your agent ​

Edge exposes its whole tool surface over MCP, so an agent can publish, promote, roll back, manage domains and read analytics on your behalf. This page connects one and proves it works.

You do this once per app. It suits everyday assistants as much as coding tools — asking Claude to roll back a site is a reasonable thing to do from your phone.

The endpoint ​

https://mcp.edge.deca-dev.com/mcp

Keep the MCP hostname, the API hostname, and your credentials on this same host family. See Environments and domains.

The bare origin https://mcp.edge.deca-dev.com reaches the same server and is its OAuth resource identifier. Client setup should use the /mcp URL because it works consistently across Claude Code, ChatGPT and other clients.

The server speaks streamable HTTP. It is not a local process, so there is nothing to install, no command to run and no npx wrapper.

Signing in ​

Edge uses OAuth. Apps that support remote MCP authentication open a browser, ask you to sign in, and store the token themselves. You do not paste an access token, and you should not need to create one.

Your organization and workspace come from whoever you sign in as. There is nothing to configure in the app.

DECA Agents ​

DECA Agents is in your DECA account. Connect Edge from inside the app. There is no URL to paste and no config file.

  1. Open DECA Agents.
  2. Go to Customize.
  3. Go to Connectors.
  4. Choose Connect on DECA Edge.
  5. Sign in when the browser asks.

When the connector is on, tools whose names start with edge_ are listed, and you can publish from the chat.

Claude ​

Custom connectors live in your Claude account settings, so adding one covers both the web app and the desktop app — there is no local config file to edit.

  1. Go to Customize → Connectors.
  2. Click +, then Add custom connector.
  3. Paste https://mcp.edge.deca-dev.com/mcp.
  4. Connect, and complete the sign-in in the browser window that opens.

On Team and Enterprise plans an owner adds the connector under Organization settings → Connectors first; members then enable it from Customize → Connectors.

Available on Free, Pro, Max, Team and Enterprise, though Free is limited to a single custom connector.

ChatGPT ​

  1. Open Settings → Apps & Connectors and turn on Developer Mode.
  2. Choose Create.
  3. Give it a name and description, and set the server URL to https://mcp.edge.deca-dev.com/mcp.
  4. Complete the OAuth sign-in.

ChatGPT needs the /mcp path

Leaving the path off is the usual reason a connector fails here. Both forms work on Edge's side; ChatGPT is the one that insists.

Developer Mode requires Plus, Pro, Business, Enterprise or Edu — it is not on the free tier. On Business and Enterprise an administrator may have to allow it before the option appears at all.

Coding agents ​

bash
claude mcp add --transport http deca-edge https://mcp.edge.deca-dev.com/mcp --callback-port 8787

# Complete OAuth when prompted. If needed, start it explicitly:
claude mcp login deca-edge
json
// .cursor/mcp.json for one project, or ~/.cursor/mcp.json for all of them
{
  "mcpServers": {
    "deca-edge": {
      "url": "https://mcp.edge.deca-dev.com"
    }
  }
}
json
// .vscode/mcp.json
{
  "servers": {
    "deca-edge": {
      "type": "http",
      "url": "https://mcp.edge.deca-dev.com"
    }
  }
}
toml
# ~/.codex/config.toml
[mcp_servers.deca-edge]
url = "https://mcp.edge.deca-dev.com"

[mcp_servers.deca-edge.oauth]
callback_port = 8788
callback_url = "http://127.0.0.1:8788/callback/nLq-cPQk3r9w"

--callback-port 8787 is only the port Claude Code listens on in this example. Any free loopback port works. Complete OAuth when asked, then run /mcp and confirm tools whose names start with edge_ are available. claude mcp login deca-edge starts the same browser flow explicitly.

Codex signs in with codex mcp login deca-edge after the server is added. That opens the browser. Codex listens on 127.0.0.1 port 8788, and the path in the callback URL is fixed for https://mcp.edge.deca-dev.com (no /mcp suffix). When it finishes, confirm tools whose names start with edge_ are available.

Anything else ​

Any MCP client that supports remote servers over streamable HTTP will work. Give it the URL above; if it also supports OAuth, that is all it needs. If it asks for a transport, choose streamable HTTP rather than SSE.

Check it worked ​

Ask for something read-only:

text
List my distributions on Edge.

It should call edge_distribution_list and come back with your sites — or an empty list, which still means the connection is good.

A 401 means sign-in did not complete; run it again. A 403 means you are connected but that call is not allowed for your account. See Permission scopes only if you need to look up what a 403 named.

Shared operations, one set of rules ​

Connecting an agent does not lock you out of anything. Most core publish, domain and analytics operations have matching HTTP routes that run the same handlers and permission checks, so you can drive a publish from your agent and inspect it with curl, or the reverse.

The surfaces are not identical. Creating and invoking function runtimes, document history/rollback, document grants, and private data objects are MCP-only, while listing an organization's workspaces is HTTP-only. The HTTP API reference marks these exceptions.

The HTTP API is a separate audience (https://api.edge.deca-dev.com) from MCP, so a token that works for one is not automatically valid for the other.

Next ​