Model Context Protocol server for social media — post and schedule from your AI client
Drop the official bundle.social MCP server into Claude Desktop, Claude Code, Cursor or any MCP-aware client and your agent gains first-class tools for posting, scheduling, media uploads and analytics across 14+ platforms.
Last updated: May 2026
1// .mcp.json — drop this into Claude Desktop, Claude Code, Cursor or any MCP client2{3 "mcpServers": {4 "bundlesocial": {5 "command": "npx",6 "args": ["-y", "bundlesocial-mcp"],7 "env": { "BUNDLESOCIAL_API_KEY": "sk_live_..." }8 }9 }10}1112// Then, in your AI client:13// "Schedule a LinkedIn + X post for Monday 9am UTC announcing the launch."14// → create_post / schedule_post tools run against bundle.socialWiring an MCP server to every social platform yourself
What bundle.social handles
Stop hand-rolling MCP tools per platform
Install bundlesocial-mcp once, point it at an API key, and every connected social account becomes a tool your agent can call. The MCP server tracks platform changes so your tool definitions don't have to.
Workflow
How it works
Connect accounts once, then create and schedule posts with channel-specific fields from one API.
Add the server to your MCP client
Drop the JSON snippet into Claude Desktop, Claude Code, Cursor or any MCP-aware client and set BUNDLESOCIAL_API_KEY.
Connect social accounts (once)
OAuth into X, Instagram, TikTok, LinkedIn, YouTube or any of the 14+ platforms from the bundle.social dashboard.
Let your agent call the tools
create_post, schedule_post, upload_media, get_analytics — all available to the agent as first-class MCP tools.
Capabilities
What the MCP server exposes
First-party tools for every workflow an agent needs around social publishing — without per-platform glue code.
Posting & scheduling tools
create_post and schedule_post handle one post for many platforms with platform-specific payload blocks. Status comes back structured.
Account & team tools
list_social_accounts, list_teams and switch_team let agents discover which accounts they can publish to before they post.
Media upload tools
upload_media accepts URLs or file paths. Returns an uploadId your agent can reference from create_post — no base64 round-tripping.
Analytics tools
get_post_analytics and get_account_analytics surface per-post and per-account metrics so the agent can close the loop on what it published.
Developer example
Add bundlesocial-mcp to any MCP client
Examples use bundle.social's public API shape: API key authentication, a post date, selected social account types, and platform-specific data.
1// .mcp.json — drop this into Claude Desktop, Claude Code, Cursor or any MCP client2{3 "mcpServers": {4 "bundlesocial": {5 "command": "npx",6 "args": ["-y", "bundlesocial-mcp"],7 "env": { "BUNDLESOCIAL_API_KEY": "sk_live_..." }8 }9 }10}1112// Then, in your AI client:13// "Schedule a LinkedIn + X post for Monday 9am UTC announcing the launch."14// → create_post / schedule_post tools run against bundle.socialSupported content
Honest limitations
- Requires an MCP-aware client (Claude Desktop, Claude Code, Cursor, or any client implementing the protocol).
- Posts created via MCP follow the same per-platform rules as posts created via SDK/API — TikTok still requires privacy, YouTube still has thumbnail rules.
- Tool surface is intentionally conservative — destructive actions (delete_account, etc.) are excluded by default; use the SDK if you need them.
Guarantees
Developer-first infrastructure
2% error rate
We handle the platform edge cases, media processing, and rate limits so your requests succeed.
Verbose errors
When native APIs fail, we return human-readable error messages and actionable recovery steps.
Flat pricing
No per-post counting. Predictable pricing for teams managing many users, workspaces, and connected accounts.
Same-day support
Direct access to the engineers building the API. We respond to technical issues the same day. Sometimes the same hour. Test us c;
Resources
Technical guides & documentation
FAQ
Questions developers ask before building
Which MCP clients does this work with?
Any client implementing the Model Context Protocol — Claude Desktop, Claude Code, Cursor, Continue, and others. The server is a plain Node process invoked via stdio, so client-specific setup is just where to put the JSON config.
Do I need to write any code?
No. Install with npx, set the API key, and the tools appear in your client. If you want to extend the surface, the same actions are available through the bundle.social SDK and REST API.
How does auth work?
The MCP server reads BUNDLESOCIAL_API_KEY from its env. The API key is org-scoped; the agent can act on any social account connected to that org's teams.
Is this the same as the CLI?
The CLI (bundlesocial-cli) is a shell-out interface — agents that exec subprocesses use it. The MCP server speaks the Model Context Protocol — clients like Claude Desktop and Cursor use it. Both wrap the same REST API.