Post, schedule, and analyze social media across 16+ platforms via the post.buzz API.
MCPpedia last refreshed this data
io.github.navneet35371/postbuzz-mcp is an MCP server that post, schedule, and analyze social media across 16+ platforms via the post.buzz API. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"postbuzz": {
"env": {
"POSTBUZZ_API_KEY": "sx_live_..."
},
"args": [
"-y",
"postbuzz-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Post, schedule, and analyze social media across 16+ platforms via the post.buzz API.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked postbuzz-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in marketing
Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.
DataForSEO API modelcontextprotocol server
Schedule posts to 10 social platforms and check drafts against hook rules learned from your audience
Newsletters where you pay for the emails you send, not for dormant subscribers, at a fraction of the price of beehiiv and the like. Open source: self-host it, or use mailcheap.ai.
MCP Security Weekly
Get CVE alerts and security updates for io.github.navneet35371/postbuzz-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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+.
Create an API key at post.buzz → Settings → API Keys (sx_live_…), then configure your client:
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"postbuzz": {
"command": "npx",
"args": ["-y", "postbuzz-mcp"],
"env": { "POSTBUZZ_API_KEY": "sx_live_..." }
}
}
}
claude mcp add postbuzz -e POSTBUZZ_API_KEY=sx_live_... -- npx -y postbuzz-mcp
~/.cursor/mcp.json:
{
"mcpServers": {
"postbuzz": {
"command": "npx",
"args": ["-y", "postbuzz-mcp"],
"env": { "POSTBUZZ_API_KEY": "sx_live_..." }
}
}
}
| 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
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.
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 }].
Tool failures return { "error": { "code", "message", "details"? } } as text content with isError: true — the same envelope the REST API and CLI emit.
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