The posting layer
for your agents.

Connect your X account once. Then Claude Code, Cursor, Codex or your own scripts post through the Octopost MCP server and API, with native threads, every character limit handled, and an approval queue when you want to look first. Threads opens once Meta approves our app; Bluesky, LinkedIn and Mastodon are in testing.Prefer to write it yourself? The web composer does the same thing.

Twitter/XLiveLinkedInIn testingBlueskyIn testingMastodonIn testingThreadsAfter Meta approval

Simple as 1, 2, 3.

01

Connect your X account

Sign in with X once. Octopost keeps the token fresh, so your agent never handles OAuth.

02

Give your agent the key

One command adds the MCP server to Claude Code. Cursor, Codex and scripts use the same key over REST.

03

Post, schedule or queue

Your agent posts now, picks a time, or queues it for your approval. A thread goes out as one reply chain.

We post through it ourselves.

Jake Marsh built Octopost and runs his own posts through it: written ahead, queued, and published by the same scheduler your agent uses. These are counts from Octopost’s database.

112
posts published through Octopost from Jake’s accounts, as of November 2, 2026
42 of 43
posts to X published successfully in the 60 days to November 3, 2026
143 of 176
posts created in those 60 days that were threads

What comes with every plan

Your agent reaches all of it through the MCP server, the API and webhooks. All of it starts at Basic.

One post, every connected account

One post goes to every account you connect, and threads stay threads. Live on X today. Threads opens once Meta approves our app; Bluesky, LinkedIn and Mastodon are in testing. Instagram, Facebook, TikTok, YouTube, Pinterest and Reddit are in platform review.

Twitter/X · LiveThreads · After Meta approvalBluesky · In testingLinkedIn · In testingMastodon · In testing

Smart scheduling

Schedule posts for a set time, or drop them in a queue that publishes at your chosen interval and hours.

M
T
W
T
F
S
S

No surprise X bills

X charges per API post, and far more for a post with a link. Each plan has a monthly X allowance, posting pauses when it runs out, and there is never an overage charge.

Plain post · 1 unitPost with a link · 13 units
How X units add up

Content calendar

A month view of what is scheduled, published and waiting for approval, so you can spot the gaps.

Approve before it posts

Queue drafts from the dashboard or your AI agent, then approve each one before it goes live.

Drafted · by you or your agent
Waiting · needs your approval
Approved · publishes on schedule
For developers

Automate everything with the API

The same API your agent uses over MCP. Post from a CI pipeline, a release script, or anywhere you can make an HTTP request. Included on every plan.

  • RESTful endpoints with JSON
  • Webhooks for publish events
  • API key authentication
Read the docs →

Guides: post to X from Claude Code, announce GitHub releases, scheduling API, approve agent posts, and a free thread splitter. All guides.

POST /api/posts
curl -X POST https://octopost.ink/api/posts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Hello from the API!",
    "platforms": ["twitter"],
    "scheduled_for": "2026-11-03T15:00:00Z"
  }'

Pricing

Every plan includes the MCP server and API. Start with 7 days for $1, then pay monthly. Cancel from your billing page.

Basic
$29/month

3 social accounts, scheduling, queue, MCP server and API.

Start for $1
Premium
$79/month

10 social accounts, 3x the X posts, priority support.

Start for $1
Business
$199/month

Unlimited social accounts, webhooks, 8x the X posts.

Start for $1

Compare all features →

Give your agent a place to post.

Connect your X account, paste one command into Claude Code, and your next post goes out from there. Plans from $29/month or $290/year. Try it 7 days for $1.

Try it 7 days for $1