Skip to main content
Connecting an MCP client to Morphic is a sign-in, not a credential you manage. Your client opens Morphic, you approve the connection, and it receives a short-lived token it renews on its own. Endpoint: https://mcp.morphic.io/v2/mcp There is nothing to put in a config file — no header, no key, no account ID.

​
Connecting

1

Add the connect URL

Add https://mcp.morphic.io/v2/mcp to your client. Clients that support OAuth discovery need no further configuration.
2

Sign in to Morphic

The first time the client needs Morphic it opens app.morphic.io and you sign in as yourself.
3

Approve

Morphic shows which client is asking, which of your workspaces it may reach, and what it may do. Choose, then approve.
4

Done

The client holds a token valid for one hour and renews it silently. Nothing long-lived is written to your machine.
You will never be asked for a Morphic password anywhere except app.morphic.io. If another page asks for your Morphic credentials, it is not us — close it.
If you decline, the server returns error=access_denied to your client as OAuth requires, and nothing is stored.

​
Your connection, your workspaces

A connection identifies you, not a workspace — but it only reaches the workspaces you ticked on the approval screen. Which one a request acts in is resolved in this order:
  1. A workspace argument on the tool call itself — every tool accepts one.
  2. ?workspace=<slug> on the connect URL: https://mcp.morphic.io/v2/mcp?workspace=acme
  3. If the grant reaches exactly one workspace, it is used automatically.
  4. Otherwise the server asks which one. Call list_workspaces for the slugs, then retry with workspace set.
The argument is what makes a multi-workspace grant usable in one conversation: the connect URL is client configuration a person has to edit, so switching workspaces used to mean reconnecting. Setting it per call needs no reconnect and changes nothing for the next call. Use ?workspace= when you want a standing default rather than a per-call choice. To work in two approved workspaces at once without naming one each time, add a second server entry with a different ?workspace=. The advertised tool list stays the same size either way.
Every request re-checks that you are still a member of the workspace being addressed. Losing access to a workspace stops that connection reaching it, without affecting your others.

​
Permission levels

The approval screen offers three levels. A client can never be granted more than it asked for, and one that asks for nothing gets Read only.
At Read and write or Full access, a connection can do what you can do in the Morphic app — including deleting records in bulk and sending real Slack messages and email. The model driving the client decides when. Approve the lowest level that client actually needs.

​
Managing and revoking connections

Each approved connection is separate. Revoke one at https://app.morphic.io/home/{workspace}/settings/developers → Connected apps. Revoking the connection you gave Cursor leaves the one you gave Claude working. Revocation takes effect within two minutes.

​
Redirect URI validation

The server only redirects back to a redirect_uri it trusts: one registered by the client during dynamic client registration (POST /v2/mcp/register, which issues an mc1_ client id), or one under a hard allowlist — https://claude.ai, https://claude.com, https://cursor.com, https://chatgpt.com, https://chat.openai.com, and loopback addresses (localhost, 127.0.0.1, [::1], any port) for local clients. Self-hosted deployments can extend the allowlist with REDIRECT_URI_ALLOWLIST.

​
Token details

Access tokens are signed, audience-bound envelopes prefixed mo_at_, valid one hour, paired with a rotating refresh token (mo_rt_). They are bound to https://mcp.morphic.io/v2/mcp per RFC 8707, so a token issued for any other resource is rejected. Tokens carry no API key and no account id — the workspace is decided per request and membership-checked.

​
Environment variables (self-hosted)

SUPABASE_URL and SUPABASE_ANON_KEY are not used. Earlier documentation listed them as required; the Supabase auth path was removed and the variables are ignored.