Connect TheTabber to Claude, Cursor, or Codex and let it draft, schedule, and publish across 9 platforms.
Posts to
launch.mp4 to all my accounts.Same account, same endpoints. Start with whichever fits your setup, and mix them if you want.
Native tool-calling for Claude Desktop, Claude Code, and Cursor. One line to install.
claude mcp add thetabber --scope user \
--env TABBER_API_KEY=ttbr_live_… \
-- npx -y @thetabber/mcpA ready-made skill that teaches your agent the TheTabber workflow (find your accounts, upload media, post or schedule, confirm results) with guardrails. Pairs with MCP or the REST API.
Add the agent-mode skill to Claude Code or your own agent, then set TABBER_API_KEY.
Any language, any framework. Bearer auth and a machine-readable OpenAPI 3 spec.
curl https://thetabber.com/v1/posts \
-H "Authorization: Bearer ttbr_live_…" \
-d '{ "caption": "New drop 🎬",
"social_accounts": ["acct_1","acct_2"],
"media": ["media_9"] }'Add the MCP server or your API key. The agent can now see your workspace.
Tell it what to post, where, and when, in plain language.
It uploads media and fans the post out to every account you named.
It reads back per-account results and retries anything that failed.
Talk to your agent in plain language. A few things people ask:
“Which social accounts do I have connected?”
“Post this photo to Instagram and TikTok with the caption 'launch day'.”
“Schedule 'new episode is out' to all my accounts for 9am Monday, New York time.”
“Upload launch.mp4 and post it to every account right now.”
“Did my last post go out everywhere? Show me any failures.”
“Cancel the post I scheduled for Friday.”
| whoami | Confirm the key and workspace |
| list_social_accounts | Fetch account UUIDs to post to |
| create_post | Publish now or schedule for later |
| get_post · update_post | Read or edit a scheduled post |
| cancel_post | Cancel before it publishes |
| upload_media | Upload a file or URL → media UUID |
| list_post_results | Per-account posted / failed outcomes |
Plus get_social_account, list_posts, list_media, get_media, delete_media, and get_post_result.
The Model Context Protocol is an open standard for wiring AI agents to tools. Our server exposes TheTabber as native tools, so agents like Claude and Cursor can post and schedule without you writing a line of HTTP.
Anything that speaks MCP: Claude Desktop, Claude Code, Cursor, and Windsurf. Plus anything that can make an HTTP request through the REST API, like Codex, cron jobs, n8n, or your own scripts.
MCP gives the smoothest native tool-calling in Claude and Cursor. The skill teaches an agent the workflow and guardrails. REST is there when you want to call it directly from any language. All three hit the same endpoints.
Create a key in your dashboard (it looks like ttbr_live_…) and pass it as a bearer token, or set it as the TABBER_API_KEY environment variable for MCP.
Yes. Point it at a local file or a public URL and it requests a presigned upload, pushes the bytes, and attaches the media. One video or up to ten images per post.
The others still go out. Each post returns per-account results, so the agent can read the failure reason and retry just the one that broke.
Agent and API access is included with your TheTabber plan. Check the pricing page for the details.
Still have a question? Get in touch.
Grab a key, connect the server, and let it start posting.