Claude plugin directory: Sume as a connector or a bundle

Claude's release notes list a developer portal for submitting plugins. For Sume, ship the hosted MCP URL in a plugin .mcp.json and keep API keys out of it.

4 min readSume
All posts

Claude's release notes, in an entry dated September 25, 2026, announce a way to build plugins for Claude: a developer portal to submit plugins to the directory, track review and see usage analytics. If you package Sume for it, the .mcp.json should contain only the hosted MCP URL and let each user sign in with OAuth, with no API key committed.

The portal facts are from the Claude release notes. The page does not spell out manifest details, so the file below is the standard remote-server shape, not a claim about the directory's review rules.

Two ways to offer Sume

Connector or plugin (read 2026-10-04)
OptionWhat users getAuth
Custom connectorOne remote server entry pointing at SumeOAuth consent on Sume
Plugin bundleThe MCP entry plus whatever else you shipOAuth consent on Sume
Directory listingSubmit through the developer portal, then track review and usagePer the Claude notes
Sume endpointhttps://mcp.sume.com/mcpmcp:read required, mcp:write opt-in

Minimal .mcp.json

Users approve scopes on Sume's consent page (OAuth docs), so nothing secret belongs in the file.

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

What to leave out

  • No API key, no bearer string, no x-api-key header.
  • No promise of write or paid tools: read-only users will not see them.
  • No claim about directory approval; that is the reviewer's call.
  • Link users to the hosted MCP docs for the tool list.

Sources

Related posts

More in Integrations

All Integrations posts

Written by Sume