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.

Rheos is built around a single integration surface today and two more on the roadmap.

​
Today — MCP

The Rheos MCP server is the primary way to drive Rheos from outside the dashboard. It exposes ~40 tools covering the full content lifecycle — brand identity, idea generation, drafting, image and video production, scheduling, publishing — and works with any Model Context Protocol client (claude.ai, Claude Code, Cursor, ChatGPT, Windsurf, etc.).

MCP overview

What the server is, why use it, supported clients.

Setup

Copy-paste configs for each client and the OAuth flow.

Tools reference

Every tool, grouped by category.

Workflows

Concrete end-to-end recipes.
If you want to wire an LLM into Rheos — or let a developer’s AI assistant post on your behalf — MCP is the right surface.

​
Roadmap

​
Webhooks

Outbound webhooks for key lifecycle events:
  • post.published, post.publish_failed, post.scheduled
  • brand.identity_updated, brand.source_added
  • credits.low, credits.purchased
  • platform.disconnected, platform.token_expiring
Useful for piping Rheos activity into Slack, Linear, Notion, or your own event bus.

​
REST API

A first-class REST surface for the same actions exposed via MCP — for backend services, scheduled jobs, and CI workflows that don’t want to host an MCP client. Will share the same API-key auth and credit model as MCP today.

​
Public app marketplace

Once webhooks and REST land, we’ll publish an app directory so partners can list integrations (CRM sync, analytics export, content sourcing, etc.) without each customer wiring it up by hand.

​
Want something specific?

If you’re blocked on an integration, email support@rheos.app with the use case. We prioritise the roadmap based on what paying customers ask for.
Last modified on May 15, 2026