Skip to main content
Find answers to common questions about Claude’s connector integrations.

General questions

Connectors are available on Free, Pro, Max, Team, and Enterprise plans. See platform availability for more details.
MCP (Model Context Protocol) is an open standard by Anthropic enabling AI applications to connect with tools and data sources. It’s the technology powering Claude’s connectors. Learn more about MCP.
Yes, Claude for iOS and Android can access remote MCP servers. You can use previously configured servers, but adding new ones must be done through the web or desktop apps.
For Team and Enterprise plans, an Owner or Primary Owner must enable connectors in Admin Settings > Connectors. Individual users can then connect through Settings > Connectors.

Authentication & security

Most connectors use OAuth 2.0 for authentication. You’ll be prompted to authorize Claude to access your account on the connected service. Your permissions on the external service determine what Claude can access.
Most first-party connectors (Google, Microsoft, Slack) are read-only—Claude can search and analyze but cannot create, edit, or delete content. Custom connectors may have different permissions; always review what you’re authorizing.
Go to Settings > Connectors, find the connector you want to remove, and click “Disconnect.” This removes Claude’s access immediately.
Anthropic collects parameters, data, and responses from MCP tool calls. For Team/Enterprise plans, this data is not used for model training. Consumer plan users who opted into model training may have content used for improvement. See data handling policies.

Technical questions

  • Claude.ai and Desktop: 300 seconds (5 minutes)
  • Claude Code: Configurable via MCP_TOOL_TIMEOUT
  • Claude.ai and Desktop: ~150,000 characters
  • Claude Code: 25,000 tokens (configurable via MAX_MCP_OUTPUT_TOKENS)
For details on how large payloads affect MCP Apps, see troubleshooting large tool results.
Common issues:
  • Authentication expired—try disconnecting and reconnecting
  • Service is temporarily unavailable
  • Permissions changed on the external service
  • Browser extensions blocking the connection
Try clearing cookies, using a different browser, or checking the external service’s status.

Custom connectors

Yes! You can build custom connectors using the Model Context Protocol (MCP). See Building Custom Connectors for details.
Submit via the Connectors Directory review form. Your MCP server must meet security and compatibility standards, and all tools must include a title and the applicable readOnlyHint or destructiveHint. Learn more about submitting custom connectors.
Claude supports OAuth 2.0 with Dynamic Client Registration (DCR), OAuth 2.0 with Client ID Metadata Document (CIMD), OAuth 2.0 with Anthropic-held client credentials, custom connection-time credentials, and authless servers. A pure machine-to-machine client_credentials grant is not supported—every connection requires user consent—but oauth_anthropic_creds provides a consent-gated alternative. See the authentication reference for details.

Directory & partnership

No, and there never will be. Directory inclusion is free.
No. There is one standard review process for all connectors and no preferred-connector designation. The directory is a level playing field. See the partnership FAQ.
No. Standard directory inclusion only requires meeting the technical requirements and agreeing to the Software Directory Policy and Terms.
No. Connector terms do not grant Anthropic rights to train on partner data. See the partnership FAQ.
Remote is strongly recommended. Local server submission exists but is a secondary path.
Same runtime infrastructure. Directory connectors add Anthropic review, in-product discovery, and eligibility for Suggested Connectors. See directory vs custom.
Yes. Anthropic’s first-party integrations appear in the directory alongside third-party connectors.
Yes. All Claude.ai connectors, including MCP Apps, are available on iOS and Android. Adding new connectors must currently be done via web or desktop.
160.79.104.0/21. See the IP address reference.