Skip to main content
The MagicPost MCP server lets any Model Context Protocol client — Claude Desktop, Cursor, claude.ai, custom agents — operate your MagicPost account from within a conversation, without leaving the chat.

What it does

  • Generates posts in your own voice — or in an imported creator’s writing style
  • Reads your analytics, lists your draft / scheduled / published posts
  • Writes new drafts, schedules posts (same-day & exact-slot warnings), cancels, publishes now
  • Finds inspiration in a global catalogue of high-performing posts
  • Detects & manages leads from your posts’ engagement, scored against your ICPs and synced to your CRM
  • Manages your org (super_admins) — read teammates’ analytics and posts, schedule on their behalf
  • Refreshes your LinkedIn data and waits for completion
It’s a thin, stateless proxy over our REST API. Everything you can do with curl, you can do via the MCP — just from an LLM conversation.

Architecture

Endpoint

Transport: streamable-http (current MCP standard, stateless mode, JSON responses).

Available tools

The server exposes 25 tools — see the full catalog.

Generation & styles

Posts

Scheduling

Analytics

Inspiration

Leads & CRM

Org / team

What it does NOT do (yet)

  • Media uploads (images, videos) — text-only for v1. Add media in the MagicPost web UI after the LLM creates a draft.
  • @mentions that need LinkedIn tag resolution — the LLM cannot pick the right LinkedIn profile from a name. Finalize @mentions in the web UI.
Most tools are scoped to your own account. Org super_admins additionally get read/scheduling access to their teammates’ posts and analytics via the *_org_* / *_member_* tools.

Next steps

Setup Claude Desktop

The flagship LLM client.

Setup Cursor

Same backend, IDE workflow.

Tool catalog

Inputs, outputs, examples for the 25 tools.

API reference

The REST endpoints behind the MCP.