Skip to content
Docs / MCP server

AI assistants

MCP server

Connect your AI assistant to Postzora, then ask it to plan, write and schedule posts in your own words.

The Model Context Protocol is how AI assistants use other apps. Postzora’s MCP server gives yours the same abilities as the API: it reads your channels and calendar, and schedules posts that go through every check the app makes.

Connect by signing in

Claude and ChatGPT connect with your Postzora sign-in, so there’s no key to copy. You choose the workspace and the access when you approve it.

Claude

  1. In Claude, on the web or the desktop app, open Settings, then Connectors, and choose Add custom connector.
  2. Name it Postzora and enter https://api.postzora.com/mcp as the URL.
  3. Choose Connect, sign in to Postzora, and pick the workspace and the access to give it.

ChatGPT

  1. In ChatGPT, open Settings, then Apps & Connectors, and turn on developer mode under the advanced settings.
  2. Create a connector with https://api.postzora.com/mcp as the server URL and OAuth as the authentication.
  3. Sign in to Postzora when asked, and pick the workspace and the access to give it.

Custom connectors depend on your Claude or ChatGPT plan. You’ll find every assistant you connected under Settings, API keys in Postzora, where you can disconnect it.

Connect with an API key

Coding assistants take an API key instead:

  1. In Postzora, open Settings, then API keys, and create a key for the workspace you want the assistant to work in. Choose Read and write to let it schedule posts.
  2. Add the server to your assistant, putting your key in place of YOUR_API_KEY.
  3. Restart the assistant, or reload its MCP servers, and check that Postzora shows up with its tools.
claude mcp add --transport http postzora https://api.postzora.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"
  • Claude Code: Run it in a terminal. Add --scope user to use Postzora in every project.
  • Cursor: In ~/.cursor/mcp.json, or .cursor/mcp.json in a project.
  • VS Code: In .vscode/mcp.json. VS Code asks for the key the first time and stores it securely.
  • Windsurf: In ~/.codeium/windsurf/mcp_config.json.

Any other assistant that supports remote MCP servers works too: the server is https://api.postzora.com/mcp, using Streamable HTTP, with a Bearer API key or OAuth sign-in.

Try it

Ask in plain language. The assistant looks up your channels and posting times on its own:

  • “What’s scheduled for next week?”
  • “Turn this blog post into a LinkedIn post and a short Bluesky one, and put them in the next free slots.”
  • “Write three tips from this document and schedule one a day from Monday at 9.”
  • “Move everything on Friday to Monday at the same time.”
  • “Did yesterday’s announcement publish everywhere?”

Good assistants show you what they’re about to schedule and ask before they publish right away or delete anything.

Tools

list_channels
The connected accounts, their ids and posting times, and the workspace time zone.
Every key
get_post_settings
Extra fields a channel needs, like a YouTube title or a Pinterest board.
Every key
next_free_slot
The next free posting time for one or more channels.
Every key
list_posts
Posts in a time window, with their status on each channel.
Every key
get_post
One post, with links to where it published or why it failed.
Every key
list_media
Images and videos in the media library, to attach by id.
Every key
upload_media
Add an image or video from the chat (ChatGPT), a public link, or a small image’s bytes.
Read and write keys
create_upload_link
Links a shell command can send a file on your computer to, for assistants that run commands.
Read and write keys
schedule_post
Schedule a post, or save a draft, with its own text per channel.
Read and write keys
reschedule_post
Move a post that hasn’t published yet.
Read and write keys
delete_post
Delete a post from Postzora.
Read and write keys

Permissions and safety

  • One workspace. The assistant only sees the workspace you chose when you connected it, or that its key belongs to.
  • Your role. It can do what you can do there and no more. When the workspace requires approvals, posts it schedules for an editor wait for review.
  • Read only access doesn’t offer the tools that make changes at all, so the assistant can look but not touch.
  • Every post is checked against each network’s limits before it’s saved, and the assistant is told exactly what to fix.
  • Disconnect any time. Disconnecting an assistant or revoking its key in Settings cuts it off straight away.

Questions about the API? Email [email protected].