Skip to main content

MCP Overview

Reactor ships a built-in Model Context Protocol (MCP) server that exposes every Reactor capability as a callable tool. Any MCP-compatible client — Claude Code, Claude Desktop, Cursor, or a custom integration — can configure the engine, generate content, publish, and read analytics without touching the UI.

What is MCP?​

MCP is an open standard for connecting AI models to external tools and data. An MCP server advertises a set of tools; the model invokes them as structured function calls during a conversation.

Reactor's server is reachable at https://app.reactor.tools/api/mcp and authenticated with a Bearer API key, which also scopes every call to your workspace. See Install the MCP to connect a client and Authentication for keys.

The server is self-describing​

There is no per-tool reference page to maintain or memorize. When your client connects, it calls the protocol's tool-listing method and reads each tool's name, description, and input schema directly. Ask your agent to "list the Reactor tools" and it will show you everything available, always current with the server.

This page summarizes what the tools cover so you know what's possible. For the exact arguments of any tool, read its schema from your client.

What the tools cover​

The tools fall into a few broad categories:

  • Engine config and writes — read the full engine config, enable or configure channels, and edit every part of the brand engine: voice, brand, positioning, writing rules, per-platform tone, audiences, and competitors. Single-record sections merge the fields you provide, so partial updates never wipe existing values.
  • Content generation — create briefs, trigger generation, poll status, read and edit drafts, move content through draft → ready → published, and refine a piece through an AI chat thread.
  • Publishing and calendar — list connected channels, publish immediately, schedule for a specific time, and list, reschedule, cancel, or view the calendar of scheduled posts.
  • Analytics — pull the full dashboard, per-content performance, top content, topic clusters, posting-time recommendations, AI insights, and Search Console data; generate UTM links; and trigger or check syncs. Automation rules can act on metric thresholds.
  • Categories and owners — create categories, tag content, assign owners, and break down performance by owner and category.
  • Visuals — generate on-brand images and kick off (and poll) image-to-video renders.
  • Email — list a connected provider's lists and templates, and send or schedule campaigns.

Context document tools​

Reference documents that ground generation can also be managed over MCP: upload a document into the engine context and list what's there.

Example prompts​

A few things you can say to a client connected to Reactor:

"Create a LinkedIn post about our new API rate limits, generate it, and schedule it for Thursday at 2pm."

"Show me the top 5 performing posts from the last 30 days across all platforms."

"Look at what's trending in our analytics and suggest three new content ideas."

"Publish the current draft of content ID abc123 to LinkedIn using our main company account."

See example workflows for multi-step recipes.

Transport and rate limits​

The server uses the MCP Streamable HTTP transport, bridged to local clients with mcp-remote. Tool calls that hit external platforms (publishing, syncing) are also subject to those platforms' own rate limits.