# Reactor

> The content engine for AI-native teams.

AI content engine: configure a brand voice once, generate platform-native content, publish/schedule, and analyze — from the UI or any MCP client.

## Docs
- [Automation Rules](https://docs.reactor.tools/analytics/automation): Automation rules let Reactor take action automatically when a condition is met. Rules run in the background and can trigger brief creation, 
- [Data Sources](https://docs.reactor.tools/analytics/data-sources): Data sources are the external analytics platforms Reactor pulls data from. Connect them in Settings  Data Sources.
- [Analytics Funnels](https://docs.reactor.tools/analytics/funnels): Funnels let you track multi-step conversion paths from content to goal completion.
- [Content Insights](https://docs.reactor.tools/analytics/insights): Insights are AI-generated observations about your content performance. They surface patterns and opportunities you might miss from looking a
- [Analytics Overview](https://docs.reactor.tools/analytics/overview): The analytics dashboard gives you a consolidated view of how your content is performing across every channel and data source.
- [Platform Deep Dives](https://docs.reactor.tools/analytics/platforms): Each connected channel has a dedicated analytics page with platform-specific metrics.
- [UTM Tracking](https://docs.reactor.tools/analytics/utm-tracking): Reactor generates UTM-tagged links for every piece of content so you can see exactly which posts are driving website traffic in Google Analy
- [Hand setup to an AI](https://docs.reactor.tools/build-with-ai/ai-setup): You don't have to set Reactor up by hand. Give an AI agent the Reactor setup skill and it will:
- [Authentication](https://docs.reactor.tools/build-with-ai/authentication): Reactor's MCP server uses API key authentication. Every request carries your key as a Bearer token, and the key identifies your workspace — 
- [Install the MCP](https://docs.reactor.tools/build-with-ai/install): Reactor runs a remote MCP server at https://app.reactor.tools/api/mcp. Clients reach it through [mcp-remote](https://www.npmjs.com/package/m
- [For LLMs](https://docs.reactor.tools/build-with-ai/llms): These docs are built to be read by AI agents as well as people. Every page is available as plain Markdown, and the whole site is published i
- [MCP Overview](https://docs.reactor.tools/build-with-ai/mcp): Reactor ships a built-in [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server that exposes every Reactor capability as a c
- [Build with AI](https://docs.reactor.tools/build-with-ai/overview): Every action in Reactor is also a [Model Context Protocol](https://modelcontextprotocol.io) (MCP) tool. That means an AI agent — Claude Code
- [Example Workflows](https://docs.reactor.tools/build-with-ai/workflows): These end-to-end workflows show how to combine MCP tools to accomplish common content tasks. Tool names are real; for each tool's exact argu
- [Content Briefs](https://docs.reactor.tools/content/briefs): A brief is the planning document that tells the AI what to write. Every piece of content starts with a brief.
- [Content Editor](https://docs.reactor.tools/content/editor): The content editor is where you review, refine, and publish generated content.
- [Content Generation](https://docs.reactor.tools/content/generation): Once a brief exists, Reactor generates full content from it using a multi-step AI pipeline.
- [Engine Configuration](https://docs.reactor.tools/getting-started/engine-config): Engine config is the core persona and strategy file that powers all AI generation. Every brief and every content generation prompt draws fro
- [Onboarding and Configuration](https://docs.reactor.tools/getting-started/onboarding): When you first log in, Reactor walks you through a workspace setup flow. This page explains each step and all available configuration option
- [Quickstart](https://docs.reactor.tools/getting-started/quickstart): There are two ways to get started with Reactor. Pick whichever fits how you work.
- [Introduction](https://docs.reactor.tools/intro): The content engine for AI-native teams. Configure your brand voice, audience,
- [Calendar](https://docs.reactor.tools/publishing/calendar): The calendar shows all scheduled and published posts across every channel in a weekly grid view.
- [Platform Connections](https://docs.reactor.tools/publishing/connections): Connections are the authenticated integrations Reactor uses to post content on your behalf. Each channel you publish on requires a connectio
- [Publish Now](https://docs.reactor.tools/publishing/publish-now): Publish Now sends a piece of content to a connected platform immediately. No scheduling, no queue -- it posts and returns confirmation.
- [Scheduling Posts](https://docs.reactor.tools/publishing/scheduling): Scheduling queues content for future publishing at a specific date and time.
- [API Keys](https://docs.reactor.tools/settings/api-keys): Reactor uses API keys to authenticate requests to the MCP server. Each key is scoped to a workspace.
- [Billing](https://docs.reactor.tools/settings/billing): Reactor uses Stripe for subscription management.
- [Team and Workspace](https://docs.reactor.tools/settings/team): Reactor supports multi-member workspaces. All content, connections, and analytics are shared within a workspace.

## Optional
- [Full docs as one file](https://docs.reactor.tools/llms-full.txt)