Skip to main content
Each guide covers one service: how to create the credential as a dedicated identity, what to paste into the connect form, and the Allowed websites value. For the model behind connectors (credential types, Agent Proxy, allowed websites, bundles), see Give Claude access.
Always connect a dedicated account for Claude (for example, claude@yourcompany.example.com), not your personal login. Anyone in a channel where the connector applies can use it through Claude, so whatever this account can reach is available to every member of those channels. See Create a dedicated account per service. Before you add a connector, see where a new connector applies.
GitHub is managed through the Claude GitHub App rather than a credential; see Configure GitHub access. Services marked (custom) aren’t in the Add a connector list. Add them with Custom connector following their guide.

Connect a service that has no guide

You can add any app that has an API as a custom connector or a custom MCP server, including services this page has no guide for. See Connect a custom service for the credential types and form fields.

When a connector fails after setup

If Claude says it can’t reach a service you connected, start with the checks at the top of Troubleshoot Claude Tag setup. Open the channel’s page from the Channels tab under Claude’s access and confirm the connector is listed in its Claude’s access table. Then rerun the test in a new thread. Two entries on the troubleshooting page cover connector failures directly: