Rheos.
Website
Social media marketing
Search visibility optimisation
Model Context Protocol
MCP
Pricing
Blog
Contact

Install guide

Connect Rheos to your AI assistant

One server URL. Sign in once, and your brand context and publishing tools are available in every conversation.

https://mcp.rheos.app

Before you start

  • 1.A Rheos account on a plan that includes MCP. See plans.
  • 2.At least one brand set up, so there is a voice to write in. Onboarding does this for you.
  • 3.Your social accounts connected in the dashboard. Publishing runs on those credentials — it cannot be authorised from the chat client.

Sign in with your Rheos account

The recommended path for every client that supports remote MCP servers. Nothing to copy, no key to keep safe, and access is revocable from the dashboard.

Claude Desktop

  1. 1.Settings → Connectors → Add custom connector.
  2. 2.Paste https://mcp.rheos.app as the server URL.
  3. 3.Sign in with the same email as your Rheos dashboard login, then approve the scopes.

claude.ai

  1. 1.Settings → Connectors → Add custom connector.
  2. 2.Paste https://mcp.rheos.app as the server URL.
  3. 3.Approve the sign-in prompt. Rheos tools appear in the tool menu of any new chat.

Claude Code

  1. 1.Run the command below in your terminal.
  2. 2.A browser window opens for sign-in. Approve it, and the tools register for the project.
claude mcp add --transport http rheos https://mcp.rheos.app

ChatGPT

  1. 1.Settings → Connectors → Create. Custom connectors need a Plus, Pro, or Business plan.
  2. 2.Paste https://mcp.rheos.app as the MCP server URL.
  3. 3.Complete the OAuth prompt with your Rheos login.

Or use an API key

For editors and scripts that cannot open a browser to sign in. Generate a key in the dashboard under Settings → MCP, then bridge the remote server over stdio with mcp-remote.

Cursor

Add the config to ~/.cursor/mcp.json, then reload the editor.

Per-project config lives at .cursor/mcp.json.

Windsurf

Add the config to ~/.codeium/windsurf/mcp_config.json, then reload the editor.

Or use the MCP panel inside Windsurf.

Any other client

npx -y mcp-remote https://mcp.rheos.app \
  --header "Authorization: Bearer rk_your_key_here"
mcp.json
{
  "mcpServers": {
    "rheos": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.rheos.app",
        "--header",
        "Authorization: Bearer rk_your_key_here"
      ]
    }
  }
}

An rk_ key carries full access to your workspace and is shown once at creation. Treat it like a password, keep it out of version control, and revoke it from the dashboard the moment a machine it lives on is out of your hands.

If something goes wrong

The sign-in prompt fails or loops.

Check you are signing in with the same email as your Rheos dashboard account. If your email is attached to more than one organisation, sign-in fails closed on purpose rather than guessing which workspace to open — contact us and we will resolve it.

The server connects but no tools show up.

Most clients only read the tool list at startup. Fully quit and reopen the app rather than starting a new chat.

A publish attempt says the account was disconnected.

Reconnect the channel in the Rheos dashboard under Settings → Connections. Access tokens for social platforms expire on the platform's schedule, not ours, and reconnecting is the only way to mint a new one.

Widgets and previews don't render.

Rich previews need a client that supports MCP UI — claude.ai, Claude Desktop, or ChatGPT. In terminal clients like Claude Code the same tools still work and return a text summary plus a dashboard link.

Still stuck?

Tell us the client and what you saw, and we'll get you connected.

Get in touchWhat Rheos MCP does