Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rheos.app/llms.txt

Use this file to discover all available pages before exploring further.

The Rheos MCP server exposes your Rheos workspace as a set of tools that any Model Context Protocol client can call. Once connected, you can ask an LLM to draft posts in your brand voice, generate or upload images, schedule a week of content, kick off video renders, or read your reference data — without leaving the chat window. The endpoint is:
https://mcp.rheos.app
It speaks the standard Streamable HTTP transport and authenticates via OAuth 2.1 (for hosted clients like claude.ai and ChatGPT) or a long-lived API key (for local CLIs like Claude Code and Cursor).

Why use it

Brand-aware drafting

Every generation tool reads the brand identity document, tone, audiences and pillars before producing copy. Posts come out on-brand, not generic.

Round-trip workflow

Ideate, draft, attach image, schedule, publish. The full Rheos lifecycle is callable as tools, so an assistant can run the loop end-to-end.

Multi-brand

rheos_list_brands returns every brand in the org. Switch context per call — no separate connections needed for agencies or teams.

Same data as the dashboard

Tool calls hit the same Firestore documents the web app uses. Anything you draft via MCP shows up immediately in the Rheos UI for review.

Supported clients

The server is generic MCP, so any compliant client works. These are the ones we test against:
ClientTransportAuthNotes
claude.ai (web)HostedOAuthAdd as a Custom Connector under Settings → Connectors.
Claude CodeHosted (HTTP) or via mcp-remoteAPI key or OAuthSee Setup.
CursorHosted via mcp-remoteAPI keyPaste config into ~/.cursor/mcp.json.
ChatGPTHostedOAuthAdd via custom connectors.
Windsurf, Zed, Continue, etc.Hosted via mcp-remoteAPI keyUse the Claude Code config as a template.
API keys are issued from Settings → MCP in the Rheos dashboard. Keys are scoped to a single user and inherit that user’s brand access.

What you can do

The server ships ~40 tools, grouped into seven areas:
  • Posts — CRUD over drafts and scheduled posts (rheos_create, rheos_get, rheos_list, rheos_update).
  • Ideation — formula-aware brainstorming and idea queues (rheos_brainstorm, rheos_generate_ideas, rheos_accept_idea, rheos_refresh_idea).
  • Publishing — schedule, publish or cancel across connected channels (rheos_schedule_post, rheos_publish_post, rheos_cancel_scheduled).
  • Images — generate, upload, save assets, one-shot draft-from-image.
  • Video — session-based editing → Lambda render → AI review loop.
  • Brand identity — read brand documents, view sources, scrape websites, trigger re-synthesis.
  • Reference — formulas, audiences, themes, platforms, credits.
See the full Tools reference for signatures and examples, or jump to Workflows for end-to-end recipes.

Security model

  • OAuth tokens and API keys are scoped to a single Rheos user.
  • The token grants the same brand access that user has in the dashboard — no privilege escalation.
  • API keys can be revoked at any time from Settings → MCP.
  • Sensitive mutations (rheos_publish_post, rheos_image_generate, video renders) consume credits identically to UI actions.

Next steps

Connect a client

Copy-paste configs for claude.ai, Claude Code, Cursor and ChatGPT.

Browse the tools

Every tool, grouped by category, with key parameters.

See it in action

Concrete patterns — draft from a URL, plan a week, review analytics.

Other integrations

Webhooks, REST API and roadmap.
Last modified on May 15, 2026