---
title: "Connect Claude to the MCP server"
description: "Add InvisibleAPI to Claude as a custom connector, sign in with OAuth, and let Claude publish to Instagram and X."
---

InvisibleAPI runs a remote MCP server at `https://api.invisibleapi.ai/mcp`. Add it to Claude as a custom connector and Claude can publish to Instagram and X, track publish jobs, and read Instagram insights for your organization.

You sign in with OAuth, so there is no API key to copy.

## What you need

- An InvisibleAPI account with an organization. To publish, the organization needs at least one connected [Instagram](/docs/social-accounts/connect-instagram/) or [X](/docs/social-accounts/connect-x/) account.
- A Claude plan with custom connectors. Free plans can add one custom connector. Pro, Max, Team and Enterprise plans can add more.

On a Team or Enterprise plan, an owner adds the connector once under **Organization settings > Connectors**. Members then find it under **Customize > Connectors** and click **Connect**.

## 1. Open the connector settings

In Claude, go to **Customize > Connectors**. Click **+ Add**, then **Add custom connector**.

## 2. Add the name and server URL

![Claude's Add custom connector dialog with the name InvisibleAPI and the URL https://api.invisibleapi.ai/mcp filled in](https://images.invisibleapi.ai/docs/connect-claude-mcp/claude-add-custom-connector.png)

1. Name the connector `InvisibleAPI`. This is the name you see in your connectors list.
2. Paste the server URL: `https://api.invisibleapi.ai/mcp`
3. Click **Continue**.

## 3. Keep the detected sign-in settings

![Authentication set to Sign in now and OAuth client set to Register automatically, both marked Detected](https://images.invisibleapi.ai/docs/connect-claude-mcp/claude-connector-authentication.png)

Claude reads the server and preselects the right options. Leave them as they are.

1. **Authentication:** Sign in now
2. **OAuth client:** Register automatically

Leave **Request headers** empty, then click **Add** at the bottom of the dialog.

## 4. Approve access in InvisibleAPI

Claude sends you to InvisibleAPI. If you are not signed in to InvisibleAPI, sign in first. Then the **Authorize access** page opens.

![InvisibleAPI Authorize access page with the InvisibleAPI organization selected and the Approve button highlighted](https://images.invisibleapi.ai/docs/connect-claude-mcp/invisibleapi-oauth-consent.png)

1. Choose the organization Claude may act in. Claude only sees the accounts, jobs and insights of that organization.
2. Click **Approve**. Claude takes you back to its home page, ready for your first prompt.

The request expires after a few minutes. If it does, start the sign-in again from Claude.

## 5. Turn it on in a chat

If the connector is not on yet, click the **+** button at the lower left of the chat box, open **Connectors**, and switch on **InvisibleAPI**.

Try a first prompt: *"List my connected social accounts."*

## What Claude can do

| Tool | What it does |
|---|---|
| `list_organizations` | Lists the organizations you can access |
| `list_social_accounts` | Lists the connected Instagram and X accounts |
| `get_organization_limits` | Shows live publishing usage against your limits |
| `create_instagram_post` | Creates an Instagram publish job |
| `create_x_post` | Creates an X publish job |
| `list_publish_jobs` | Lists publish jobs and their status |
| `show_publish_job` | Shows one job in detail, including failure reasons |
| `cancel_publish_job` | Cancels a job before it is dispatched |
| `retry_publish_job` | Retries a job that failed with a retryable error |
| `get_instagram_account_insights` | Reads Instagram account insights |

## Good to know

- **Connecting a social account stays a human step.** You connect Instagram and X in the dashboard. Claude works with the accounts that are already connected.
- **Approve drafts before Claude creates a job.** A created job publishes unless something cancels it. Ask Claude to show you the drafts first, then let it create the ones you approve.
- **Schedule for a safety window.** A job can be scheduled instead of published right away, and canceled before it is dispatched.
- **API key instead of OAuth.** OAuth is the path we recommend. A scoped API key also works: send it in a `Bearer` header, or add it to the URL as an `apiKey` query parameter in Claude's connector form.