Claude directory drops MCPB: remote vs local server, and Sume
Claude's directory no longer accepts MCPB desktop extensions. A remote HTTPS server needs no package; here is what that means for Sume.
If you were planning to ship a local MCP server to Claude users as an MCPB desktop extension, that path closed: Anthropic's directory documentation says desktop extension listings are deprecated and the directory no longer accepts local MCP servers packaged as MCPB; a local server must go inside a plugin bundle. A remote MCP server is different. It is a URL, with no package and no repository. Sume's hosted MCP at https://mcp.sume.com/mcp is that kind of server, so for Sume users nothing about MCPB changes, and a custom connector pointed at that URL keeps working as before.
The directory facts below are from Anthropic's Publish to the directory page, read 2026-10-01. The Sume facts are from MCP overview and OAuth and API keys. Sume does not claim a Claude directory listing here; this is about how the two kinds of server differ.
Remote connector or plugin bundle: what is the difference?
Anthropic's page lists two submission kinds. A plugin bundle is a folder with skills, commands, agents, hooks and MCP server references, sourced from a public GitHub repository. An MCP connector is one remote MCP server that people connect to, sourced from the server's URL. Anyone on a paid Claude plan can submit, and every submission is checked; connectors are scanned automatically and by default listed as Community connectors.
| Question | Local server as MCPB | Remote MCP connector | Sume hosted MCP |
|---|---|---|---|
| Accepted by the directory? | No (deprecated) | Yes, as an MCP connector | Not a local server |
| What you ship | A packaged extension | A server URL, no repository | URL https://mcp.sume.com/mcp |
| Where it runs | On the user machine | On the vendor server | On Sume servers |
| Sign-in | Local config | OAuth or other server auth | OAuth with mcp:read, optional mcp:write, or an API key |
What does that change for someone using Sume?
Nothing you install. There is no Sume extension to keep updated, and no process on your laptop. Add the URL as a custom connector, sign in, and call tools_list. The consent page is on the MCP host and defaults to read-only; turn Write on if Claude should generate media, because paid tools return insufficient_scope without mcp:write.
For a plugin author who wants to bundle Sume, the bundle's MCP server reference would point at the same URL. Anthropic's page recommends submitting a remote server as a connector even when a plugin already references it, so one set of tools shows up instead of two.
Limits
Sume ships no local server to package anyway; the hosted URL is the only endpoint. Anthropic's directory is a separate decision from whether your own workspace can add a custom connector; custom connectors depend on your plan, and Anthropic's page does not cover them. Check Anthropic's pages for plan limits before rolling this out to a team.
Sources
Related posts
More in Comparisons
- Claude Message Batches 100,000 requests vs a Sume bulk run of 100
A Claude Message Batch holds 100,000 requests or 256 MB. A Sume bulk run queues 1 to 100 Format runs with a concurrency window of 1 to 16. Plan accordingly.
- Claude batch canceled or expired results: billed? Sume cancel billing
Claude does not bill canceled or expired batch requests. Sume bills generation a run finished before a cancel, so a cancel stops spend but never refunds.
- Claude Message Batches queue limits by tier vs Sume bulk runs
Claude's batch queue holds 200,000 requests on Start and up to 500,000 on Scale. A Sume bulk run takes 1 to 100 items, 16 at once. Different jobs.
- Cloudflare Stream clip API vs Sume video trim: start and end
Cloudflare Stream clips by posting a source UID with startTimeSeconds and endTimeSeconds. Sume video-trim takes start plus end or duration, returning a new MP4.
Written by Sume