MCP Server
One MCP server for every social account
If your agent speaks MCP, it can post, reply, like, follow and send direct messages through your own accounts on 12 platforms. Add one URL and sign in.
- URL
https://mcp.buzztake.com/mcp- Transport
- Streamable HTTP
- Sign-in
- OAuth 2.1, PKCE, dynamic registration
- Or
Authorization: Bearer btk1_...
What your MCP client can do in your social accounts
The server is at https://mcp.buzztake.com/mcp and speaks streamable HTTP, protocol versions 2025-06-18, 2025-03-26 and 2024-11-05. Each action type is one tool with the name and the parameters of the REST action, so post posts and read_feed reads the feed.
A client signs in with OAuth 2.1. It reads the server's metadata, registers itself, opens BuzzTake in the browser and gets a token with PKCE, which it renews. A client without OAuth sends an API key as Authorization: Bearer.
Besides the actions, the server has tools for accounts and sign-in links, the calendar and approvals, media uploads, credits and feedback. It also offers resources such as buzztake://prices, and prompts such as announce and plan_a_week.
It works on X, Instagram, LinkedIn, Bluesky, TikTok and YouTube, and on every other platform BuzzTake connects. Each action is one tool, named as in the actions reference.
Jobs for your MCP client
Say it in plain words. These are prompts that work, and the calls they make.
Post from every brand account at once
run_on_accountsruns one action on up to 100 accounts, all or nothing, and returns one result per account.Post 'Version 2.4 is out' from all five brand accounts.
5 × post50 credits ($0.50)Answer the newest comments
The agent reads the notifications, picks the questions and replies to each from the account they were asked.
Read my X notifications and reply to every question about pricing with a link to our pricing page.
1 × read_notifications, 3 × reply28 credits ($0.28)Find people and follow them
searchwithkind: peoplefinds accounts by topic, andfollowfollows the ones you pick.Search Bluesky for people who post about local-first software and follow the ten most active.
1 × search, 10 × follow34 credits ($0.34)Plan a week for review
The
plan_a_weekprompt walks the agent through drafts on the calendar and a review request.Plan one LinkedIn post a day next week as drafts, and submit them for review.
5 × create_content10 credits for each draft that goes outReport what BuzzTake cannot do
When you ask for something no tool does, the server's instructions tell the agent to call
send_feedbackand to tell you. It costs nothing.Schedule a TikTok live for Friday. If you cannot, send BuzzTake feedback.
No charge
Set up your MCP client
Most clients need the URL only and sign in with OAuth on the first call.
Add the URL
Add a remote server with streamable HTTP. Most clients read this shape; some name the key
serverUrlorhttpUrl, and VS Code usesserverswithtype: http.MCP config { "mcpServers": { "buzztake": { "url": "https://mcp.buzztake.com/mcp" } } }Sign in
On the first call the server answers 401 with a pointer to its OAuth metadata. The client registers itself and opens BuzzTake: sign in, check the app name, the address it returns to and the permissions, and select Allow. Only owners and administrators can allow an app.
Or send an API key
For a client without OAuth, make a key under Developers in the app with only the permissions the agent needs, and send it as a header.
MCP config { "mcpServers": { "buzztake": { "url": "https://mcp.buzztake.com/mcp", "headers": { "Authorization": "Bearer btk1_..." } } } }Check it
Ask the client to call
whoamiorlist_accounts. Both are free.Prompt Who am I in BuzzTake, and which accounts can I use?
Ways to connect your MCP client
The routes that reach BuzzTake from your MCP client, and how well each one fits.
- Remote MCP, OAuth sign-inBest fit
The client registers itself and gets a token that lasts an hour and is renewed with a refresh token. There is nothing to install and no key to keep.
- Remote MCP, API keyWorks
A key in the
Authorizationheader. A wrong key fails atinitialize, so the client knows at once.- Local stdio bridgeWorks
For a client that starts only local stdio servers, the
mcp-remotepackage forwards stdio to the remote server and does the OAuth sign-in in your browser.MCP config { "mcpServers": { "buzztake": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.buzztake.com/mcp" ] } } }- REST APIWorks
Every tool call is also a REST call, for agents that run commands.
POST /v1/accounts/{id}/actions curl https://api.buzztake.com/v1/accounts/$ACCOUNT_ID/actions \ -H "Authorization: Bearer $BUZZTAKE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"type": "post", "text": "Version 2.4 is out.", "wait": 60}'
What it costs
BuzzTake charges in prepaid credits for the actions it runs. One credit is one US cent.
| Job | Credits | USD |
|---|---|---|
| Post from every brand account at once | 50 | $0.50 |
| Answer the newest comments | 28 | $0.28 |
| Find people and follow them | 34 | $0.34 |
| Plan a week for review | 10 per post | $0.10 per post |
| Report what BuzzTake cannot do | 0 | $0.00 |
A post, a quote or a message is 10 credits, a reply 8, a like or a follow 3, and a read or a search 4. A planned post costs nothing until it goes out. Reads are charged when they succeed, and a write that fails before the page changes is refunded.
Your agent's model use is billed by its own vendor, not by BuzzTake. Every price is on the pricing page, and the rules are in Credits.
Approvals and safety
A person can approve before anything goes out, and every action is recorded.
Every read tool is marked read-only and every write tool as one that reaches the outside world; delete_post is marked destructive. Clients that read these hints can ask before a write.
An OAuth client asks for permissions, and the token gets the ones the user's role allows: integrations_manage for accounts, content_publish for writes, inbox_read for reads, content_approve for approvals.
- Ask for drafts when a person must check first.
create_contentputs the post on the calendar,submit_for_reviewsends it to a reviewer, and it goes out only after the approval. - Give the agent an API key without the
content_publishpermission. It can then plan drafts and send them for review, and it cannot post by itself. - BuzzTake records every action: who asked, through which key, on which account, what the page returned and what it cost.
- A sign-in step that BuzzTake cannot finish, such as a 2FA code, becomes a challenge. The agent asks you for the code, or gives you a link to a live browser where you answer it.
- Only an owner or an administrator can allow an OAuth client. Disconnect it under Developers in the app, and its token stops working.
More in Approvals and Reports and audit.
Limits
- One request body is at most 1 MiB. Upload media from an https URL with
upload_mediarather than as base64. - One POST runs at most 150 seconds. A session ends after 24 hours without a request, and the client starts a new one.
- The server sends nothing between requests, so
resources/subscribeis not offered over HTTP. - An action tool waits up to 120 seconds for its result. A longer action comes back with its id, and
get_actionfollows it to the end. - The MCP server runs up to 8 requests at a time for one key or sign-in. Above that it answers 429 with
Retry-After, and the client tries again. - One organization connects up to 200 accounts.
- The platforms set their own pace. When one asks an account to slow down, the action ends with
rate_limited, and a write that failed before the page changed is refunded.
Troubleshooting
Every error code and its fix is in Errors and challenges.
- The client connects with SSE and fails
- BuzzTake serves streamable HTTP. Pick that transport, or the key that means it:
httpUrlin Gemini CLI,type: httpin Claude Code and VS Code,transport: streamable-httpin OpenClaw. - 403 from the server
- The request came from a web page on another origin. Call the server from the client, not from a browser page.
- 404 for the session
- The session expired or was made with another key. The client sends
initializeagain. - The client says the server refused the token (401)
- The sign-in expired or was revoked, or the API key is wrong. Sign in again from the client, or make a new key under Developers.
- An action stops at
needs_input - The platform asked for a code. Give the code to the agent so it calls
answer_challenge, or open the challenge'ssign_in_urland answer in the live browser. - The answer is
insufficient_credits - The balance is lower than the price, and nothing was queued. A post needs 10 credits. Top up, then ask again.
- The answer is
unsupported - The platform has no such action. The error lists the actions it has, and the generic
browseraction can do the rest step by step. - An account shows
signed_out - Its session ended and no stored password could sign it in again. Ask the agent for a sign-in link with
get_sign_in_linkand open it, or reconnect the account in the app.
MCP Server questions
- What is the BuzzTake MCP server?
- A remote MCP server that gives an AI agent your social media accounts. Each action, such as post, reply, like or send_message, is a tool, and it runs in your own signed-in account.
- Which MCP clients work with it?
- Any client that speaks streamable HTTP and either OAuth 2.1 or a Bearer header. This includes Claude, ChatGPT, Claude Code, Codex, Cursor, Gemini CLI, VS Code, OpenClaw and Hermes Agent.
- Can I test the server with curl?
- Yes. A POST without a token answers 401 with the OAuth metadata address, and with an API key you can send initialize and then tools/call.
- What does a tool call cost?
- The same as the REST action. A post is 10 credits, a reply 8, a like 3 and a read 4. Account and credit tools are free.
Related agents
All AI agents, the MCP server docs, the quickstart, and the platforms: X Instagram LinkedIn Bluesky TikTok YouTube
Give your MCP client your social accounts.
Add an account with a password, cookies or a sign-in link, then connect the MCP server and ask.