---
title: MCP quickstart
description: Connect Cursor or Claude to hosted Sume MCP.
---

Connect a remote MCP client to Sume's production endpoint, complete OAuth (or
use an API key), then call a read-only discovery tool.

## 1. Use the production URL

```text
https://mcp.sume.com/mcp
```

Do not paste API keys into chat. Prefer the OAuth connector flow for interactive
clients.

## 2. Connect Claude Code

```bash
claude mcp add --transport http sume https://mcp.sume.com/mcp
claude mcp login sume
```

Confirm the server is connected in Claude Code's MCP status UI, then ask Claude
to call `tools_list` or `mcp_health`.

## 3. Connect Cursor

Add a remote MCP server entry (Cursor Settings → MCP, or your MCP config file):

```json
{
  "mcpServers": {
    "sume": {
      "url": "https://mcp.sume.com/mcp"
    }
  }
}
```

Complete the OAuth sign-in when Cursor prompts you (consent is on the MCP host,
not `app.sume.com`). After connect, call `tools_list` once to verify the
session.

## 4. Connect Codex or other HTTP MCP clients

Point a streamable HTTP MCP server at:

```text
https://mcp.sume.com/mcp
```

Run that client's OAuth login for the configured server name. The client should
discover Sume protected-resource metadata from the MCP endpoint and send you to
`https://mcp.sume.com/oauth/consent`.

## 5. Verify with a read-only tool

Ask the agent:

```text
Call the Sume MCP tool tools_list and summarize the available tools. Live ids
use underscores (tools_list, generate_image). Dotted aliases also work.
```

Useful first calls:

| Tool | Why |
|---|---|
| `mcp_health` | Confirms endpoint, auth source, and safety posture. |
| `tools_list` | Lists every tool visible to this session. |
| `tools_schema` | Returns one tool contract by `name`. |
| `account_me` | Confirms workspace account context. |
| `catalog_list` | Lists public API capabilities (broader than MCP tools). |

## 6. Know the OAuth scopes

Default hosted OAuth grants **read-only** access (`mcp:read`). Turn **Write**
on at consent to also receive `mcp:write`. There is no `mcp:paid` scope.

With `mcp:read` only:

- Read tools such as `jobs_list`, `assets_get`, `catalog_list`, and
  `crawl_scrape` work.
- Write tools such as `jobs_cancel` or `assets_create` return
  `insufficient_scope`.
- Paid tools such as `generate_image` or `avatars_create` return
  `insufficient_scope`.

To run write or paid MCP tools: grant `mcp:write` on consent, use an API-key
remote MCP session, or use the Developer API / CLI. See
[OAuth and API keys](/mcp/oauth) and [Tools and gates](/mcp/tools-and-gates).

## Local CLI alternative

If the agent can run shell commands on your machine, prefer direct CLI commands
today (`sume login`, `sume tools list --json`, Avatar submit + `sume jobs …`).
See the [CLI overview](/cli).

```bash
sume login
sume mcp doctor --json
```

Local `sume mcp` is **not launched** in current CLI releases (`coming_soon`).
It is a separate future surface from the hosted connector at `mcp.sume.com`.
Prefer hosted MCP when the client speaks remote HTTP MCP.

## Studio Agent is different

Studio Agent is the in-app Sume agent product. It is **not** the public hosted
MCP connector documented on these pages. Do not configure Studio Agent internals
as a customer MCP server URL.