Connect your AI to your social media calendar

What MCP is, in one paragraph

The Model Context Protocol (MCP) is an open standard that lets AI assistants use external tools. A tool like Postika publishes an MCP server; you add its URL to your assistant once; from then on the assistant can call that server's tools when you ask it to. No copy-pasting between tabs, no browser extensions, no API code. ChatGPT and Claude on their own cannot post to Instagram or LinkedIn; connected to a scheduler through MCP, they can put posts straight into your calendar. The MCP glossary entry goes deeper.

What your AI can do in Postika

Postika's MCP server is small on purpose. It exposes five tools, and every action follows the same rules as the app:

create_post takes a mode: schedule, approval (pending your OK in the app), draft or now (publish immediately). Dates are always in the project's local time, so "Tuesday at 9:00" means 9:00 where that brand is.

Approval first, by default

Letting an AI publish to a brand's account is a reasonable worry. That is why Postika's server instructs the AI to prefer approval unless you explicitly ask it to schedule or publish. A request like "Write five LinkedIn posts for next week" ends with five posts marked pending approval in your calendar. Nothing goes live until you open them, check the preview and approve.

When you trust a workflow, you can say "schedule them directly" and the AI will use schedule. Or "publish now" for something urgent. The choice stays with you, and you can see every post the AI created in the calendar. This is what an approval workflow looks like when the first drafter is an AI agent.

Connect your assistant

The server URL is the same for every client: https://postika.app/api/mcp. Clients that support MCP authorization open a Postika window where you sign in and click Allow.

• Claude: Settings, Connectors, Add custom connector. Name it Postika, paste the URL, click Connect and Allow. It also appears in Claude Desktop and the mobile apps.
• ChatGPT: Settings, Apps & Connectors, Advanced settings, turn on Developer mode. Then Create, paste the URL, choose OAuth and Allow.
• Claude Code: run claude mcp add --transport http postika https://postika.app/api/mcp, then /mcp to authenticate. Add --scope user to use it in every project.
• Cursor: one-click add from the Connect AI page in the app, or add the server to ~/.cursor/mcp.json.
• VS Code: MCP: Add Server, HTTP, paste the URL, or commit .vscode/mcp.json.
• Gemini CLI: add it to ~/.gemini/settings.json as httpUrl, then run /mcp auth postika.
• Other agents: clients without OAuth use a project API key in the Authorization: Bearer header. The app can copy a ready-made configuration.

Full technical details are in the MCP docs.

Prompts that work well

Good prompts give the AI the project, the networks, the timing and the mode. A few that work out of the box:

• "Draft three LinkedIn posts about our launch and leave them for my approval on Monday, Wednesday and Friday at 9:00."
• "What is scheduled for next week? Move nothing, just give me a summary."
• "Turn this blog post into a Threads post and an X post and schedule both for tomorrow at 18:30."
• "For each client project, find days next week without a post and propose one, in approval mode."
• "Delete the drafts I created yesterday in the Acme project."

The AI checks the channels first, so it knows that a Threads post must fit in 500 characters and an X post in 280. If a post breaks a limit, Postika rejects it and the AI can shorten it and try again. Our guide on how to manage social media with AI has full workflows.

Photos and videos

MCP carries text, not files, so the AI cannot upload images or videos to Postika. Instagram, TikTok, Pinterest and YouTube require media, so for those networks the AI creates the post as a draft or pending approval with the caption ready, and you attach the photo, carousel images or video in the app before approving. For Facebook, X, LinkedIn and Threads, text-only posts are allowed, so the AI can complete them end to end.

Automations without chat: n8n, Make and Zapier

Not every workflow needs a conversation. Postika's REST API, with per-project API keys, lets automation platforms create posts when something happens: a new blog article, a product added to your store, a row in a spreadsheet. Setups are documented for n8n, Make and Zapier in the automations docs. Combine both: an automation creates pending posts, and you ask your assistant on Monday to review what is waiting.