Claude Connectors: What They Are and How to Add One

A Claude connector links Claude to another app, so Claude can read from it or act in it during a chat: your calendar, your docs, your issue tracker, or a publishing tool. Some connectors come from Claude's directory and connect in one click. Any other service that runs a remote MCP server can be added by its URL as a custom connector.

The short version: open Customize › Connectors in Claude, then either connect one from the directory or choose Add custom connector and paste the server's URL. Every plan can add custom connectors; the Free plan is limited to one. Turn a connector on per chat from the "+" menu, approve its actions as Claude asks, and remove it any time from the same Connectors page.

What are Claude connectors?

Connectors are how Claude uses tools outside the chat. Under the hood most of them are MCP servers: MCP (Model Context Protocol) is the standard way an AI assistant calls an outside service's tools. A connector for a publishing tool, for example, might offer tools to list your channels, draft a post and schedule it. Claude decides when to call a tool, and you approve what it does.

How to add a connector from the directory

Claude's connector directory lists ready-made connectors. Open the listing, choose Connect, and sign in to the service when it asks. The service shows its own consent screen, which tells you what Claude will be allowed to do there. Skryvo is listed there, for instance: its directory page connects in one click and then shows Skryvo's consent page.

How to add a custom connector

These are the steps from Anthropic's help article on custom connectors, for Pro and Max accounts:

1. Go to Customize › Connectors.
2. Click + Add, then Add custom connector.
3. Enter a name and the remote MCP server URL, then click Continue.
4. Check the sign-in settings Claude detected, choose how to sign in, then click Add.

To use it in a conversation, click the "+" button at the bottom left of the chat, open Connectors and switch it on.

Which Claude plans can use custom connectors?

Anthropic lists custom connectors for Free, Pro, Max, Team and Enterprise plans, on Claude, Claude Desktop and Cowork. Free accounts can add one custom connector. On Team and Enterprise, an Owner adds the connector for the organization under Organization settings › Connectors, and each member then connects it with their own account, so Claude only reaches what that person can access.

Are Claude connectors safe?

As safe as the server behind them. Anthropic's own advice, in short:

• Custom connectors are not verified by Anthropic, so connect only servers you trust.
• Read the permissions on the service's sign-in screen before you approve.
• Choose "Allow always" only for tools you trust; otherwise approve each action.
• Turn off tools you do not need, and switch off tools that can write before using Research mode, which can call tools without asking.

A good connector also makes the risky step explicit. Skryvo's tools tell Claude to show you each post and wait for your go-ahead before scheduling it, and nothing is published without that step.

How to remove a connector

Go to Customize › Connectors and choose Remove (or the three dots next to the connector). You can also revoke access from the other service's own security settings, which cuts Claude off at the source. To change a custom connector's URL, remove it and add it again.

What can you do with a connector? One worked example

With Skryvo connected, Claude can work with your brands, connected channels, calendar and results. Things people ask:

• "Write a LinkedIn and Bluesky post about our launch week."
• "What is scheduled on my Skryvo calendar this week?"
• "Which channel and hour worked best for me last month?"

The same server works in Claude Code, ChatGPT, Cursor and other agents; the agents page has the steps for each, and our LinkedIn MCP guide covers what to check before connecting anything to a social account.

Start with one connector you will use every day, approve its actions by hand for a week, and only then decide which tools deserve "Allow always".