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

General questions

Connectors are available on Pro, Max, Team, and Enterprise plans. Free plans do not have connector access. See available integrations per plan for 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
Tool results are limited to 25,000 tokens.
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 readOnlyHint or destructiveHint. Learn more about submitting custom connectors.
OAuth 2.0 is the recommended method. IP allowlisting is available but not recommended as the sole security measure. Machine-to-machine (client credentials) flows aren’t supported.