MCP quickstart
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
Do not paste API keys into chat. Prefer the OAuth connector flow for interactive clients.
2. Connect Claude Code
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):
Complete the OAuth sign-in when Cursor prompts you. 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:
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
Sume sign-in at app.sume.com.
5. Verify with a read-only tool
Ask the agent:
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 Phase-1 OAuth limit
Hosted OAuth Phase 1 grants read-only access (mcp:read).
With OAuth:
- Read tools such as
jobs.list,assets.get, andcatalog.listwork. - Write tools such as
jobs.cancelorassets.createare denied. - Paid tools such as
avatars.createare denied.
To run write or paid MCP tools today, use an API-key remote MCP session or the Developer API / CLI. See OAuth and API keys and 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.
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.