Skip to content
BuzzTake
Sign inGet started
MenuClose

Cursor by Anysphere

Cursor writes the launch thread from the diff

The Agent already knows what changed in the code. With BuzzTake in mcp.json it can turn the diff into a thread, post it, and answer the questions that come back.

Get startedSet up Cursor
Connects through
Remote MCP, OAuth with PKCE
Config
~/.cursor/mcp.json
Tools show in
Customize, MCPs
Run mode
Auto-review, Allowlist or Run Everything
Cursor, sample run. Cursor's Agent reads a diff that adds CSV and JSON export, asks to run the BuzzTake post tool, and posts a four-part X thread about the change after the user selects Run.

What Cursor can do in your social accounts

Cursor's Agent reads the branch: the diff, the commits, the README. A launch thread written from that is exact about what shipped, and with BuzzTake the Agent posts it through your own accounts.

~/.cursor/mcp.json gives BuzzTake to every project, and .cursor/mcp.json shares it with the team in the repo. Cursor signs in with OAuth and PKCE and registers itself as a public client. The agent CLI reads the same file.

Since Cursor 3.6 the default run mode is Auto-review: tools on your allowlist run at once, and other calls go to a classifier that allows them, blocks them or asks you. Keep BuzzTake's posting tools off the allowlist.

It works on X, Reddit, LinkedIn, Bluesky and Threads, and on every other platform BuzzTake connects. Each action is one tool, named as in the actions reference.

Jobs for Cursor

Say it in plain words. These are prompts that work, and the calls they make.

  1. A launch thread from the diff

    The Agent reads the branch, writes a four-post thread about what changed for users, and posts it after you read it.

    Write a 4-post X thread about what this branch changes for users, from the diff and the commits. Show it to me, then post it.

    1 × post10 credits ($0.10)

  2. The changelog to your subreddit

    On a release, the Agent posts the changelog to your project's subreddit with a title and the full notes.

    Post the 2.4 changelog to r/acme_demo with the title Acme 2.4 released.

    1 × post10 credits ($0.10)

  3. Answer the questions under the launch

    It reads the replies to the launch post, answers the technical questions from the code, and asks you before each reply.

    Read the replies to our launch post on X and answer the technical questions from the code. Ask me before each reply.

    1 × read_post, 4 × reply36 credits ($0.36)

  4. A screenshot on LinkedIn

    The Agent uploads the new screenshot from the repo and posts it with a short caption.

    Upload docs/img/dashboard.png and post it on our LinkedIn page with a two-line caption about the new dashboard.

    1 × post10 credits ($0.10)

  5. A morning check with an Automation

    A Cursor Automation runs as you every morning, reads the mentions and opens a summary in your project.

    Every morning, read our X notifications and search X for acme-sdk with BuzzTake, and summarize the new bug reports.

    1 × read_notifications, 1 × search8 credits ($0.08)

Set up Cursor

Cursor and BuzzTake need only the URL. The sign-in runs in your browser.

  1. Add the server

    Put it in ~/.cursor/mcp.json for all projects, or in .cursor/mcp.json to share it with the team.

    ~/.cursor/mcp.json
    {
  "mcpServers": {
    "buzztake": {
      "url": "https://mcp.buzztake.com/mcp"
    }
  }
}

  2. Sign in

    Open Customize, MCPs. Sign in to BuzzTake from its entry: BuzzTake opens in your browser; select Allow.

  3. Check the run mode

    Open Settings, Agents, Approvals & Execution. Auto-review or Allowlist both work; keep post, reply and send_message off the allowlist.

  4. Ask the Agent

    Start with a read, which changes nothing.

    Prompt
    List my BuzzTake accounts and read the latest 10 X notifications.

Ways to connect Cursor

The routes that reach BuzzTake from Cursor, and how well each one fits.

Remote MCP, OAuth sign-inBest fit

Cursor registers itself as a public client and signs in with PKCE. Cloud Agents sign in separately, per person.

Remote MCP, API keyWorks

Set BUZZTAKE_API_KEY in your shell profile; Cursor reads it with ${env:BUZZTAKE_API_KEY}.

~/.cursor/mcp.json
{
  "mcpServers": {
    "buzztake": {
      "url": "https://mcp.buzztake.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:BUZZTAKE_API_KEY}"
      }
    }
  }
}
Remote MCP, OAuth sign-inWorks

The agent CLI reads the same file. --approve-mcps approves the MCP servers for a headless run.

Terminal
agent mcp login buzztake
agent -p --approve-mcps "Read my X notifications with BuzzTake"
REST APIWorks

The Agent can run curl in the terminal, after an approval. MCP keeps the terminal free.

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.

Credits for each job on this page
JobCreditsUSD
A launch thread from the diff10$0.10
The changelog to your subreddit10$0.10
Answer the questions under the launch36$0.36
A screenshot on LinkedIn10$0.10
A morning check with an Automation8$0.08

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.

Cursor's model use is billed by Anysphere, 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.

Run modes are Auto-review, Allowlist and Run Everything. In Auto-review, allowlisted tools run at once and a classifier decides on the rest, which can mean a prompt. Do not use Run Everything with tools that post.

For a second person, have the Agent plan drafts with create_content and submit_for_review, and approve them in BuzzTake.

  • Ask for drafts when a person must check first. create_content puts the post on the calendar, submit_for_review sends it to a reviewer, and it goes out only after the approval.
  • Give the agent an API key without the content_publish permission. 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

  • Cloud Agents take HTTP or stdio servers, not SSE or mcp-remote. Their sign-ins are separate from the editor's.
  • An Automation runs without its tools when the MCP sign-in fails, and shows an MCP authentication failed event.
  • An action tool waits up to 120 seconds for its result. A longer action comes back with its id, and get_action follows 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 Agent does not use BuzzTake
Check Customize, MCPs: BuzzTake must be on and signed in. Name BuzzTake in the prompt.
An Automation ran without BuzzTake
Its MCP sign-in failed. Sign in to BuzzTake for Cloud Agents at cursor.com/agents.
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's sign_in_url and 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 browser action 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_link and open it, or reconnect the account in the app.

Cursor questions

Can Cursor post to social media?
Yes. With BuzzTake in mcp.json, Cursor's Agent posts, replies and reads your accounts on 12 platforms, from the editor, the agent CLI or a Cloud Agent.
Will the Agent post without asking?
Not if the posting tools are off the allowlist. In Auto-review, a call that is not allowlisted goes to a classifier that can ask you, and BuzzTake drafts add a reviewer.
Does a .cursor/mcp.json in the repo share my sign-in?
No. The file shares the server address. Each person signs in to BuzzTake for themselves.
What does a launch thread cost?
A thread is one post action, 10 credits. Each reply to the questions under it is 8 credits.

Related agents

All AI agents, the MCP server docs, the quickstart, and the platforms: X Reddit LinkedIn Bluesky Threads

Cursor is a trademark of Anysphere. Platform names belong to their owners. BuzzTake is not affiliated with or endorsed by Anysphere or any platform.

Give Cursor your social accounts.

Add an account with a password, cookies or a sign-in link, then connect the MCP server and ask.

Get startedRead the MCP docs