Work in progress — early access only. Public rollout coming soon. Email hello@rheos.app if you’d like an invite.
- Log in with Rheos (OAuth) — used by chat tools like claude.ai and ChatGPT. You select “Connect”, get bounced to rheos.app to approve, and you’re done. No keys to copy.
- API key — used by local tools like Claude Code, Cursor, and other CLI clients. Generate a key in Settings → MCP, paste it into the client’s config.
Pick whichever your tool supports. Most chat tools use OAuth; most local tools use API keys.
Generate an API key
Create a key
Select Generate new key, give it a label (e.g. “Cursor laptop”), and copy the secret. You’ll only see it once.
Store it safely
Treat the key like a password. Anyone with it can act as you in Rheos. Revoke unused keys from the same screen.
Client setup
claude.ai
Claude Code
Cursor
ChatGPT
Other clients
Claude.ai uses OAuth — no API key needed.Open Connectors
In claude.ai, select your avatar → Settings → Connectors → Add custom connector.
Add Rheos
- Name:
Rheos
- URL:
https://mcp.rheos.app
Select Add.Authorize
Claude.ai will redirect you to rheos.app to sign in and approve. After approval you’ll be bounced back with the connection active.
Test
Start a new chat and ask: “What Rheos brands do I have?” Claude should call rheos_list_brands and return your brands.
Claude Code can connect either directly (HTTP transport) or through the mcp-remote shim. Direct HTTP is preferred where the client supports it.Option A — direct HTTP (~/.claude/settings.json):{
"mcpServers": {
"rheos": {
"type": "http",
"url": "https://mcp.rheos.app",
"headers": {
"Authorization": "Bearer rk_live_your_api_key_here"
}
}
}
}
mcp-remote (works everywhere npx does):{
"mcpServers": {
"rheos": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.rheos.app",
"--header",
"Authorization: Bearer rk_live_your_api_key_here"
]
}
}
}
/mcp to reload). You should see rheos listed under connected servers. Edit ~/.cursor/mcp.json (create it if it doesn’t exist):{
"mcpServers": {
"rheos": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.rheos.app",
"--header",
"Authorization: Bearer rk_live_your_api_key_here"
]
}
}
}
ChatGPT’s custom connector framework is rolling out gradually. If you don’t see the option in your account, fall back to claude.ai or Claude Code in the meantime.
Open Connectors
In ChatGPT, go to Settings → Connectors → Create.
Add Rheos
- Name:
Rheos
- MCP Server URL:
https://mcp.rheos.app
- Authentication: OAuth
Save.Authorize
ChatGPT will open a rheos.app window for sign-in and consent.
Any MCP client that supports the Streamable HTTP transport will work. The
pattern is always the same:npx -y mcp-remote https://mcp.rheos.app \
--header "Authorization: Bearer rk_live_your_api_key_here"
mcp-remote package handles the HTTP-to-stdio bridge. Verifying the connection
Once connected, any of these prompts should produce a tool call:
- “List my Rheos brands.” →
rheos_list_brands
- “What’s my Rheos credit balance?” →
rheos_get_credits
- “Show me the formula tree.” →
rheos_get_formulas
If the client returns “no tools available”, check:
- The Authorization header is exact —
Bearer prefix included, no trailing whitespace.
- The key hasn’t been revoked. Re-check Settings → MCP in the dashboard.
- Your client supports the Streamable HTTP transport (most do as of 2026).
Never commit API keys to git. Use environment variables, a secret manager, or the client’s native credential store.
Rotating or revoking keys
Open Settings → MCP in the Rheos dashboard. Each key shows its last-used
timestamp. Select Revoke to invalidate it immediately — any client using
that key will start returning 401 within seconds.
To rotate, generate a new key first, update your client config, then revoke
the old one.
