---
title: "Connect Claude to 1Post over MCP"
url: "https://get1post.com/assistants/claude.md"
canonical_url: "https://get1post.com/assistants/claude"
last_updated: "2026-10-26"
type: "how-to"
summary: "Add the 1Post MCP server to Claude: the exact settings, how to sign in or use a key, and a request and reply to check it works."
related: ["https://get1post.com/assistants.md", "https://get1post.com/docs/mcp.md", "https://get1post.com/docs/mcp-oauth.md", "https://get1post.com/docs/api-authentication.md"]
---

# Connect Claude to 1Post over MCP

Add the 1Post MCP server to Claude: the exact settings, how to sign in or use a key, and a request and reply to check it works.

Connect Claude to 1Post by adding the MCP server at https://api.get1post.com/v1/mcp with your API key, or at https://api.get1post.com/v1/mcp/oauth to sign in. Claude then lists your accounts, schedules posts and reads results with your role. The steps and the exact Claude settings are below; actions that cancel or reply need confirmation.

## Set up Claude

1. Open connectors. In Claude, open Customize, then Connectors. On a Team or Enterprise plan an owner adds the connector under Organization settings, then Connectors.
2. Add a custom connector. Choose Add, then Add custom connector. Give it a name such as 1Post and enter https://api.get1post.com/v1/mcp/oauth.
3. Sign in. Under Authentication choose Sign in now and approve access to the workspace you want.
4. Use it. Ask Claude to list your 1Post accounts. Members of a Team or Enterprise plan open Customize, then Connectors, and choose Connect.

## The Claude settings

To use a key instead of signing in, enter https://api.get1post.com/v1/mcp, choose No sign in, and add a request header named Authorization with the value Bearer op_live_YOUR_KEY.

Custom connectors are available on the Free plan (one connector), Pro, Max, Team and Enterprise.

## A request and its reply

Once connected, Claude sends tool calls like this one when you ask it to schedule a post. Account ids come from list_accounts.

**Tool call**

```json
{
  "name": "create_post",
  "arguments": {
    "accounts": [
      "ACCOUNT_ID"
    ],
    "text": "Doors open at nine.",
    "schedule_at": "2026-11-02T15:00:00Z"
  }
}
```

**Reply, abridged**

```json
{
  "id": "POST_ID",
  "status": "scheduled",
  "scheduled_at": "2026-11-02T15:00:00.000Z",
  "accounts": [
    {
      "account_id": "ACCOUNT_ID",
      "status": "queued"
    }
  ]
}
```

## What the connection can do

| Tool | What it does | Needs |
| --- | --- | --- |
| list_accounts | Lists connected accounts and their state | Read |
| create_post | Saves, schedules or publishes a post | Write |
| get_post | Reads one post and the result for each account | Read |
| cancel_post | Cancels a post that has not started | Write and confirm: true |

The connection acts with the role of the member who made the key or signed in, so a contributor's posts still go to review. The full tool list is on the [MCP page](https://get1post.com/docs/mcp.md).

## Questions

**Who can add the connector on a team plan?**

On Team only Owners can add it. On Enterprise Owners and members with a custom role that manages libraries can. Everyone else connects from Customize, then Connectors.

**What can Claude do once it is connected?**

It can list your accounts, create and update posts, read results and analytics, and cancel or reply when you confirm. It cannot do more than the member behind the key or sign-in.

## Sources

- [Claude help center: custom connectors using remote MCP](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), read 2026-10-26

## Related

- [Connect an assistant to 1Post over MCP](https://get1post.com/assistants.md)
- [The MCP server: 1Post docs](https://get1post.com/docs/mcp.md)
- [MCP sign-in with OAuth: 1Post docs](https://get1post.com/docs/mcp-oauth.md)
- [API authentication and keys: 1Post docs](https://get1post.com/docs/api-authentication.md)