MCP quickstart

Connect a remote MCP client to the Sume 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. For interactive clients, the OAuth connector flow is the preferred method.

2. Connect Claude Code

In the Claude Code MCP status UI, make sure that the server is connected. 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):

When Cursor prompts you, complete the OAuth sign-in. The consent page is on the MCP host, not app.sume.com. After you connect, call tools_list one time to make sure that the session works.

4. Connect Codex or other HTTP MCP clients

Set the URL of a streamable HTTP MCP server to:

Run the OAuth login of the client for the configured server name. The client will discover the Sume protected-resource metadata from the MCP endpoint. Then the client will send you to https://mcp.sume.com/oauth/authorize. This URL continues to https://mcp.sume.com/oauth/consent.

5. Verify with a read-only tool

Ask the agent:

Useful first calls:

Tool	Why
`mcp_health`	Confirms the endpoint, the auth source, and the safety posture.
`tools_list`	Lists all the tools that this session can see.
`tools_schema`	Returns one tool contract by `name`.
`account_me`	Confirms the workspace account context.
`catalog_list`	Lists the public API capabilities (more than the MCP tools).

6. Know the OAuth scopes

By default, hosted OAuth grants read-only access (mcp:read). To also get mcp:write, set the Write toggle to on at consent. There is no mcp:paid scope.

If the session has only mcp:read:

Read tools, for example jobs_list, assets_get, catalog_list, and crawl_scrape, work.
Write tools, for example jobs_cancel or assets_create, return insufficient_scope.
Paid tools, for example generate_image or avatars_create, return insufficient_scope.

To run write or paid MCP tools, grant mcp:write on consent. As an alternative, use an API-key remote MCP session or the Developer API / CLI. Refer to OAuth and API keys and Tools and gates.

Local CLI alternative

If the agent can run shell commands on your machine, direct CLI commands are the preferred method today (sume login, sume tools list --json, Avatar submit + sume jobs …). Refer to the CLI overview.

Local sume mcp is not launched in the current CLI releases (coming_soon). It is a future surface, separate from the hosted connector at mcp.sume.com. When the client supports remote HTTP MCP, hosted MCP is the preferred method.

Studio Agent is different

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