> For the complete documentation index, see [llms.txt](https://docs.slatecx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slatecx.com/guides/connect-mcp-clients.md).

# Connect MCP clients

SlateCX exposes two Model Context Protocol servers. They serve different audiences and are authorized separately.

| Server     | Endpoint      | Who connects                                              |
| ---------- | ------------- | --------------------------------------------------------- |
| Tenant MCP | `/mcp/tenant` | A tenant user, from their own MCP client                  |
| Slate MCP  | `/mcp/slate`  | A prospect, continuing a saved Slate in ChatGPT or Claude |

## Tenant MCP

### Authorize

A grant binds one connection to one explicit active tenant membership. You approve the connection in Admin at `/mcp/authorize`.

If you belong to one eligible tenant, that tenant is fixed in consent. If you belong to several, you select one before choosing permissions. Superuser status never grants implicit tenant access.

### Scopes

| Scope                        | Grantable to         | Requires                     |
| ---------------------------- | -------------------- | ---------------------------- |
| `tenant:configuration:read`  | Any active member    | —                            |
| `tenant:slates:read`         | Any active member    | —                            |
| `tenant:configuration:write` | Active tenant admins | Configuration read           |
| `tenant:destructive:write`   | Active tenant admins | Configuration read and write |

Destructive access is never preselected and is consented separately.

### Tools

Tenant MCP registers 22 read-only tools covering tenant context, campaigns, sources, cards, branding, entry-point presentation, jobs, and source knowledge retrieval, plus Slate evidence and reporting.

The authoring catalog adds 24 focused tools covering campaigns and agent configuration, sources and cards, tenant experience, and prompt pills.

Slate-backed reporting excludes preview-created Slates while retaining real archived history.

### Endpoints

```
POST   /mcp/tenant
GET    /mcp/tenant/status
DELETE /mcp/tenant
GET    /.well-known/oauth-authorization-server/tenant-mcp
GET    /.well-known/oauth-protected-resource/mcp/tenant
POST   /tenant-mcp/oauth/token
POST   /tenant-mcp/oauth/revoke
```

## Slate MCP

Slate MCP lets a prospect continue a saved Slate inside ChatGPT or Claude. ChatGPT and Claude are certified peers around the same portable MCP and MCP Apps core.

### Canonical endpoints

| Environment | URL                                         |
| ----------- | ------------------------------------------- |
| Staging     | `https://staging-app.slatecx.com/mcp/slate` |
| Production  | `https://app.slatecx.com/mcp/slate`         |

`GET` and `DELETE` on the MCP endpoint return `405` with `Allow: POST`.

### Authorization

Public-client authorization code with S256 PKCE, refresh rotation, and revocation. The prospect sees the requesting client host before any input, on the Wallet consent route `/oauth/authorize`.

```
GET  /.well-known/oauth-protected-resource
GET  /.well-known/oauth-authorization-server
GET  /oauth/authorize
POST /oauth/token
POST /oauth/revoke
```

### Returning to Wallet

`POST /slates/:slateId/session/slatecx-token-transfer` redeems a return token into a normal Wallet participant session.

## See also

* [MCP](/concepts/mcp.md)
* [API keys](/guides/api-keys.md)