Add Sume to Claude as a custom connector (remote MCP)

To add Sume to Claude as a custom connector, go to Customize > Connectors, click "+" and then "Add custom connector", paste https://mcp.sume.com/mcp, and click "Add". Sume's docs name hosted MCP with OAuth as the interactive connector for Claude, and Sume's consent page grants Read and leaves Write off unless you switch it on.

Claude's steps come from its Help Center article Get started with custom connectors using remote MCP, dated August 11, 2026; the Sume side comes from MCP quickstart, OAuth and API keys, and MCP tools and gates. All were read on 2026-09-27. Sume has no official Claude connector: this is a custom connector pointed at Sume's hosted MCP server. For the Claude Code CLI, see Connect Claude Code, Cursor, or Codex to Sume.

Which Claude plans and apps support custom connectors?

Custom connectors using remote MCP are available in Claude, Cowork, and Claude Desktop on Free, Pro, Max, Team, and Enterprise plans; Free users are limited to one custom connector. Claude connects to the server from Anthropic's cloud infrastructure, not from your device, so the server must be reachable over the public internet. https://mcp.sume.com/mcp is Sume's production URL.

• Pro and Max: Customize > Connectors, "+", "Add custom connector", paste the URL, then "Add".
• Team and Enterprise: only Owners can add custom connectors. An Owner opens Organization settings > Connectors, clicks "Add", hovers over "Custom", selects "Web", pastes the URL, and clicks "Add".
• Team and Enterprise members then open Customize > Connectors, find the connector (it usually has a "Custom" label), and click "Connect" to authenticate. Each member connects individually.

What happens when I sign in?

Claude's article says adding a custom connector typically goes through an OAuth sign-in, which lets Claude act on your behalf without ever seeing your password, and that you can revoke those permissions at any time by disconnecting the connector. On Team and Enterprise plans, each member signs in separately when they click "Connect".

Sume's quickstart says to prefer the OAuth connector flow for interactive clients. Sume's OAuth docs describe that flow for remote MCP clients in general, not Claude's screens: consent happens on mcp.sume.com, not app.sume.com, with Read locked on and a Write toggle that is off by default. Sume's MCP OAuth flow walks through each step.

Should I turn on Write?

Leave Write off unless Claude should change things or spend. A read-only mcp:read session can call read tools such as jobs_list, assets_get, catalog_list, and crawl_scrape, while write tools such as jobs_cancel and assets_create, and paid tools such as generate_image and avatars_create, return insufficient_scope. Write adds mcp:write, which exposes mutating and paid tools. There is no mcp:paid scope: paid submits still need an idempotency_key and pass wallet admission. Claude's own controls sit on top of Sume's scopes:

How do I check that it works?

Ask Claude to call mcp_health, which confirms the endpoint, the auth source, and the safety posture; for an OAuth session, authenticated.auth_source is mcp_oauth. Then ask for tools_list, which lists every tool visible to the session. A tool that returns insufficient_scope means the session lacks mcp:write; see how to fix insufficient_scope. To change a custom connector later, Claude's article says to remove it and add it again.

What can't the connector do?

The Sume docs list these limits:

• Hosted MCP cannot read files from your laptop.
• Hosted MCP does not mirror the whole HTTP API; the docs say to discover the live contract with tools_list and tools_schema rather than assume parity.
• An MCP OAuth token is not a Sume API key, and the docs say not to mint API keys for hosted OAuth clients as a workaround.
• Hosted MCP still works but is not part of the primary path today, according to Sume basics; a product integration calls a Format or the Developer API.
• The in-app Studio Agent is a separate product surface, not this connector.