Morphic MCP

Connect URL current release 0.4.0

One endpoint, streamable HTTP. You sign in with Morphic — there is no key to create, copy or store.

Connect in 30 seconds

Pick your client. Every block below is complete as written — paste it in, and approve the connection when Morphic asks.

claude mcp add --transport http morphic https://mcp.morphic.io/v2/mcp

{
  "mcpServers": {
    "morphic": {
      "url": "https://mcp.morphic.io/v2/mcp"
    }
  }
}

{
  "mcpServers": {
    "morphic": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.morphic.io/v2/mcp"]
    }
  }
}

{
  "mcpServers": {
    "morphic": {
      "url": "https://mcp.morphic.io/v2/mcp"
    }
  }
}

{
  "servers": {
    "morphic": {
      "type": "http",
      "url": "https://mcp.morphic.io/v2/mcp"
    }
  }
}

https://mcp.morphic.io/v2/mcp

How connecting works

1. Add the connect URL to your client. Nothing else to configure.
2. The first time it needs Morphic, your client opens app.morphic.io and you sign in as yourself.
3. Morphic shows what the client is asking for. Choose which of your workspaces it may reach, pick a permission level, and approve.
4. The client receives a token that lasts an hour and renews itself. Nothing long-lived is stored on your machine.

The connection is yours, not a workspace's. Only the workspaces you tick on the approval screen are reachable. If you approved exactly one, it is used automatically. If you approved several, every tool takes an optional workspace argument, so the assistant can switch between them mid-conversation — ask it to call list_workspaces first. To pin one workspace as the default for every call instead, put it on the URL:

https://mcp.morphic.io/v2/mcp?workspace=acme

Add a second server entry with a different ?workspace= to work in two at once without naming one each time. The tool list stays the same size either way.

No password is ever entered outside app.morphic.io. If any other page asks you for Morphic credentials, it is not us.

What a connection can do read this

It writes and it deletes

create_entity, update_entity and set_entity_field change CRM records. delete_entity, bulk_delete_entities, bulk_delete_activities and bulk_delete_notes remove them, in bulk, in one call. Morphic does not stage these for review and does not ask you to confirm before one runs — the client is the only place a confirmation step can exist.

It sends real messages to real people

post_to_slack and post_to_telegram post into your workspace's connected channels, and agentmail_action sends actual email. To everyone who receives one, a message an agent sent is indistinguishable from one you sent. agentmail_action lives in the addons group, which is off by default — it becomes reachable only if you opt in with ?tools=…,addons.

Reduce the blast radius

• Approve the lowest permission level the client actually needs. Read only cannot change or delete anything.
• Approve only the workspaces that client needs to see, not all of them.
• Give each client only the groups it needs: ?tools=schema,entities,activities. See Choosing a tool subset.

Revoke it

Morphic app → your workspace → Settings → Developers (/home/{account}/settings/developers) → Connected apps → revoke. Each connection is separate, so revoking the one you gave Cursor leaves the one you gave Claude working. Revocation takes effect within two minutes.

Verify it works

Once a client is connected you can call the ping tool directly to separate "not connected" from "bad client config". Substitute the access token your client obtained.

curl -sS https://mcp.morphic.io/v2/mcp \
  -H "Authorization: Bearer $MORPHIC_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ping","arguments":{}}}'

A live connection returns a server-sent event whose payload contains pong — morphic-mcp v0.4.0:

event: message
data: {"result":{"content":[{"type":"text","text":"pong — morphic-mcp v0.4.0"}]},"jsonrpc":"2.0","id":1}

Anything else:

• 401 — not connected, or the connection expired or was revoked. Reconnect from your client.
• 406 — you sent a GET. The command above is a POST; a GET opens the SSE stream and needs Accept: text/event-stream.
• 429 — too many attempts from your IP. Wait 60 seconds.

Tools (270 total)

Rendered from the server's own tool registry, so this list is what the server actually serves. 35 groups plus ping, which is always registered on every profile.

The addons group is excluded by default (-addons,-clay) — those tools are billed separately and only work once installed for the workspace.

Choosing a tool subset

Every client downloads the whole tool catalog on connect, before anyone has typed anything. All 270 tools are a large JSON schema. A CRM-only profile is about a third of that payload — and a third of the context those definitions occupy for the rest of the session.

Per connection: ?tools=

Append the parameter to the connect URL. It is resolved per request, so two clients can hold different profiles against the same server.

https://mcp.morphic.io/v2/mcp?tools=schema,entities,activities

Syntax

Group ids are listed next to each group under Tools. Unknown ids are ignored rather than rejected, so a stale URL degrades to a working connection. ping is always present, however narrow the profile.

For AI agents

Limits & errors

Reference

Machine-readable version catalog: GET /mcp with Accept: application/json, or /mcp?format=json. Liveness and running release: /health.