A social media MCP server for your AI agent
Connect an assistant to real publishing tools, then make the destination, media and saved result explicit. Start with one reviewed draft.
A social media MCP server gives a compatible AI assistant tools for working with connected accounts and posts. It bridges the gap between a conversation that writes a caption and a system that stores or publishes it. Blitz Planner’s server can read account capabilities, create and update posts, schedule them and inspect publishing history.
MCP is the connection protocol. It does not make every assistant compatible with every server, or remove the need to review a publishing action.
Configure the client before requesting a post
Blitz’s MCP endpoint is https://mcp.blitz-planner.com/mcp. The current server uses a Blitz API key in an authorization header or x-blitz-api-key. Use a client that supports this configuration and keep the key in its credential settings.
The developer settings in Blitz require signing in. They provide the setup for supported clients including Cursor, Codex and Claude Code. Other clients need compatible transport, authentication and permission to use write tools. See the MCP tool concepts for how assistants discover and call tools.
Read the destination before writing
Ask the assistant to select the project, list its accounts and check publishing capabilities. Use an exact account ID when several accounts share a network. If an account needs reconnecting or a format is unsupported, resolve that before preparing a write action.
Useful Blitz tools include:
| Tool | What it does |
|---|---|
blitz_list_accounts | Lists accounts in the selected project |
blitz_get_capabilities | Reads publishing capabilities |
blitz_upload_media_from_urls | Imports accessible existing media |
blitz_create_post | Creates a post, with the requested state and settings |
blitz_update_post | Edits a saved post or its schedule |
blitz_schedule_post | Creates a new scheduled post |
blitz_get_calendar | Reads scheduled posts |
blitz_get_history | Reads publishing history |
Scheduling a new post and editing an existing draft are different operations. Ask the assistant to preserve the existing post ID when updating a reviewed draft.
Try one draft with a precise brief
An illustrative first request:
List the accounts in my chosen project. After I select one, create a draft with this caption and the reviewed media. Do not schedule or publish. Return the post ID, selected account and saved status.
For blitz_create_post, a draft request omits scheduledAt and leaves publishNow false or unset. Review the saved post in Blitz before adding a date. A request to “create a post” without a clear state is too ambiguous for an unattended publishing action.
Bring finished media to the agent
The public tools work with existing media. They do not run Atelier’s product-URL-to-week, faceless rendering or Seedance generation workflows. Prepare those assets in the app, review them, then use the agent to manage the publishing post.
A video script alone is not a video file. An imported image must match the selected network’s capabilities. TikTok also needs its creator settings and final posting consent checked.
Read back the saved result
After a write, check the post’s saved state and calendar entry. For publication, check history and the destination result. A post ID, scheduled state or accepted request does not prove that the content is already public.
Keep the review concrete: caption, media, account, date, timezone and posting mode. Those are the details another person should be able to verify without rereading the whole conversation.
Practical guides from the makers of Blitz Planner. Product examples describe the current workflow; examples and prompts are illustrative.