What the names mean
| Anthropic term | Meaning |
|---|---|
| Connector | A user-facing integration powered by MCP. It may be prebuilt, directory-listed, or a custom remote connection. |
| Desktop extension / MCPB | A packaged local MCP server for Claude Desktop. |
| Plugin | A broader package for Claude Code or Cowork that may bundle MCP connections, skills, commands, and subagents. |
| MCP App | Optional interactive UI rendered inside compatible Claude web or desktop conversations. |
Remote and local are different products
Remote connector
Runs behind an internet-reachable endpoint
Claude’s cloud connects to the server, even when the user is in Desktop or Cowork. Users authenticate individually, and Team/Enterprise owners control organization availability.
Local MCP
Runs on the user’s computer
Claude Desktop and Claude Code can launch local processes. A localhost server configured this way does not become a connector in Claude web, mobile, or Cowork.
Claude’s official surface matrix gives remote MCP broad reach across web, mobile, Cowork, Desktop, and Claude Code. Local servers are limited to local-capable products. Remote requests may require firewall allowlisting because they originate from Anthropic infrastructure.
Adding a connector
Individuals use Claude’s connector settings to add a remote URL and authenticate. On Team and Enterprise plans, an owner first enables the connector for the organization; members then connect their own service accounts. Directory listings can be Verified or Community. Those labels describe Anthropic’s review level—not a different protocol or a guarantee that every workflow is safe.
Authentication and compatibility
- Remote connectors support no-auth and several OAuth patterns, including dynamic registration and client metadata approaches.
- Every remote connection requires user consent; Claude’s connector product is not a machine-to-machine service-account channel.
- Do not put tokens in URLs. Keep credentials in the authorization flow or supported secure configuration.
- Claude currently documents a defined subset of MCP features and protocol versions. Implement negotiation and graceful fallback rather than assuming every draft capability is present.
- Connector result sizes and tool runtimes are bounded; long jobs should return explicit state rather than holding a single call open indefinitely.
Progressive tool exposure
Claude Code has verified MCP Tool Search. It can defer full MCP tool definitions and find them when a request needs them. Anthropic also exposes Tool Search in API tooling. Do not automatically extend that behavior to every Claude web, mobile, or Cowork surface.
Good fit
Use a remote connector when the same service should be available across several Claude surfaces. Use a desktop extension or local server when the capability belongs to one machine. Use a plugin when the job also needs packaged skills, commands, or agent behavior—not merely a connection.