Cursor team MCP servers: share Sume's hosted MCP across a team

To share Sume's hosted MCP server across a Cursor team, add it as a team server in Cursor's dashboard, or commit it to a project's .cursor/mcp.json so everyone in the repository gets it. Each person should sign in with their own OAuth consent rather than share one API key, because a shared key gives every teammate the same spending power.

The Cursor facts come from Cursor's MCP documentation, read 2026-09-29. The Sume facts come from its MCP quickstart and OAuth pages.

Where can a Cursor MCP server live?

Cursor's page lists a project file, a global file and team-managed servers.

What is the Sume entry?

The entry is a url, as Sume's quickstart shows. Cursor's page says url and headers are the remote-server options.

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

How does sign-in work for each person?

With no header, Cursor starts the OAuth flow and consent appears on the MCP host. Default consent is read-only (mcp:read); a person who wants the paid tools switches Write on, which adds mcp:write. There is no mcp:paid scope. So a team can share the entry while each person decides their own access.

What changes if the team shares one API key?

A key gives the full hosted tool set, and spend goes through wallet and admission checks. Every teammate using it can start paid generations. If you do share one, keep it out of the committed file, use Cursor's header support with a secret, and ask each agent to preview with dry_run=true and pass max_spend_usd.

Sume's docs say not to store OAuth tokens as keys and to rotate an API key if it appears in logs or chat.

How do I keep the tool list manageable?

Cursor's docs say it uses MCP tools listed under Available Tools when relevant. Sume's tool set is long, so check the guidance on tool limits and keep the model's choice small for tasks that only need video.