About post.buzz
post.buzz is an MCP server that exposes the post.buzz social media API to MCP clients for publishing, scheduling, and analytics across platforms. Its tools also cover accounts, comments, inboxes, media, teams, CSV imports, and video clipping.
Key features
- 01Create, schedule, and manage posts
- 02Manage comments and inbox replies
- 03Upload and manage media
- 04View post and account analytics
- 05Manage social accounts and teams
- 06Import CSVs and create video clips
Use cases
- 01Schedule social content across platforms
- 02Review account performance and best posting times
- 03Handle comments, mentions, and direct messages
- 04Create short clips from long videos
MCP support
It exposes 51 social media tools to MCP clients and can run locally or through post.buzz's hosted Streamable HTTP endpoint.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y postbuzz-mcpPOSTBUZZ_API_KEYSecretpost.buzz API key (Settings → API Keys, sx_live_…)POSTBUZZ_API_URLAPI base URL override (default https://post.buzz/api)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
55Saved tool list · updated 4d ago
This tool takes no parameters.
Details
From the project READMEpostbuzz-mcp
MCP (Model Context Protocol) server for the post.buzz social media API — post, schedule, and analyze across 16+ platforms from Claude Desktop, Claude Code, Cursor, or any MCP client.
A thin, transport-agnostic wrapper over the official postbuzz SDK, mirroring postbuzz-cli. Requires Node.js 20+.
Setup
Create an API key at post.buzz → Settings → API Keys (sx_live_…), then configure your client:
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"postbuzz": {
"command": "npx",
"args": ["-y", "postbuzz-mcp"],
"env": { "POSTBUZZ_API_KEY": "sx_live_..." }
}
}
}
Claude Code
claude mcp add postbuzz -e POSTBUZZ_API_KEY=sx_live_... -- npx -y postbuzz-mcp
Cursor
~/.cursor/mcp.json:
{
"mcpServers": {
"postbuzz": {
"command": "npx",
"args": ["-y", "postbuzz-mcp"],
"env": { "POSTBUZZ_API_KEY": "sx_live_..." }
}
}
}
Configuration
| Env var | Flag | Required | Purpose |
|---|---|---|---|
POSTBUZZ_API_KEY | --api-key | yes | API key |
POSTBUZZ_API_URL | --api-url | no | API base URL (default https://post.buzz/api) |
Test interactively with the MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.js
Tools (51)
Diagnostics — check_setup (run it first), describe_platform (per-platform field schemas; call before create_post).
Organization — get_organization, get_usage.
Accounts — list_accounts, get_account, connect_account (OAuth URL), disconnect_account, refresh_account, list_account_tools, run_account_tool (Reddit flairs / Pinterest boards).
Posts — create_post, schedule_post, list_posts, get_post, update_post, delete_post, retry_post, reschedule_post.
Comments — create_comment (immediate or scheduled; parentCommentId chains replies), list_comments, get_comment, update_comment, delete_comment, retry_comment.
Inbox — list_inbox (comments/mentions/DMs), reply_to_inbox_item, edit_inbox_reply.
Media — upload_media (public URL or local image/video/PDF path — other file types are refused), list_media, get_media, delete_media, delete_media_many.
Analytics — get_post_analytics, get_account_analytics, get_bulk_post_analytics (≤ 60 posts), refresh_analytics, get_analytics_summary, get_best_times.
Teams — list_teams, get_team, create_team, update_team, delete_team, add_team_account, remove_team_account.
CSV import — create_post_csv_import, list_post_csv_imports, get_post_csv_import, get_post_csv_import_rows, retry_post_csv_import.
Clipping — create_clip (long video → short clips, async, idempotent), list_clips, get_clip, get_clip_usage.
Every tool carries MCP annotations: get_*/list_*/describe_* are readOnlyHint, delete_*/disconnect_*/remove_* are destructiveHint, so clients can auto-approve reads and confirm deletes.
Targeting & per-platform fields
Posts target accounts by id (list_accounts); per-platform required fields (Reddit sr-style lookups, Pinterest boards, TikTok privacy, YouTube madeForKids…) are discovered via describe_platform + run_account_tool and passed through accountOverrides[{ accountId, fields }].
Errors
Tool failures return { "error": { "code", "message", "details"? } } as text content with isError: true — the same envelope the REST API and CLI emit.
Hosted endpoint
post.buzz also serves these tools at https://post.buzz/api/mcp
(Streamable HTTP), so no local install is needed:
claude mcp add --transport http postbuzz https://post.buzz/api/mcp \
--header "Authorization: Bearer sx_live_…"
The hosted server has no access to your files: upload_media takes URLs only.
Embedding
postbuzz-mcp/server exports createServer(options) and
handleMcpRequest(request, options) — the latter serves one stateless
Streamable HTTP request with Web-standard Request/Response, for hosting
the tools on Workers, Deno, Bun, or any fetch-style server.
Development
bun install
bun run build # tsup → dist/index.js
bun run test # vitest: MCP client over in-memory transport (manifest + flows)
node test/live-stdio.mjs # live integration over real stdio (needs POSTBUZZ_API_KEY)
createServer({ apiKey, apiUrl? }) (exported from dist/index.js) builds the transport-agnostic McpServer.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.