Set up Claude Code
- 01
Make a key
In 1Post, open Settings, then API keys, and make a key with write scope. Copy it once; it begins with op_live_.
- 02
Add the server
Run the add command with the HTTP transport and the key as a header.
- 03
Check the connection
Start Claude Code and ask it to list your 1Post accounts. It calls list_accounts and prints the result.
The Claude Code settings
claude mcp add --transport http 1post https://api.get1post.com/v1/mcp \
--header "Authorization: Bearer op_live_YOUR_KEY"claude mcp add --transport http 1post https://api.get1post.com/v1/mcp/oauthAfter adding the server without a key, run /mcp inside Claude Code and follow the browser steps to sign in. Claude Code stores the tokens and refreshes them.
A request and its reply
Once connected, Claude Code sends tool calls like this one when you ask it to schedule a post. Account ids come from list_accounts.
{
"name": "create_post",
"arguments": {
"accounts": [
"ACCOUNT_ID"
],
"text": "Doors open at nine.",
"schedule_at": "2026-11-02T15:00:00Z"
}
}{
"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.