Start from the dashboard, then use Riley from AI tools, team channels, and connected workflows where supported. Your dashboard, MCP and API, Claude, Cursor, ChatGPT where supported, and Slack. Sign in once, mint a key, and Riley shows up in the tools you already use, with the same approval rules everywhere.
Pick the path that fits you. Both start by signing in at app.hireriley.com. The dashboard needs no key at all, and neither does Slack.
app.hireriley.com/login.https://app.hireriley.com/mcpx-api-key: YOUR_RILEY_KEY (Authorization: Bearer also works)Live means we run and document it end to end. Beta means it is in testing. Where supported means it depends on your plan. MCP compatible means it should work with guided setup, though we have not individually verified that client.
The full product in your browser, no setup beyond signing in. This is the control center and the source of truth.
The raw endpoint for anything that speaks the protocol, with per-workspace keys.
Connect Riley as an MCP server and work from Claude Desktop.
Add Riley with one command and use it from the terminal.
Add Riley as an MCP server in Cursor settings.
Works where ChatGPT supports custom MCP connectors on your plan.
One optional team channel: requests, drafts, approvals, and receipts. No key needed.
Outbound only: Riley sends reports and alerts. It does not take tasks by inbound email yet.
In testing. Setup is guided by the Riley team.
Guided setup with the endpoint and key. Not individually verified.
Guided setup with the endpoint and key. Not individually verified.
Add Riley under mcp_servers in your Codex config. Not individually verified.
Add an MCP server in your settings. Not individually verified.
Add an MCP server in your Copilot or VS Code settings. Not individually verified.
Add an MCP server in Windsurf's Cascade settings. Not individually verified.
Add an MCP server in your agent configuration. Not individually verified.
Open WebUI, LM Studio, LibreChat, VS Code, and more. Guided setup, not individually verified.
Bring your own MCP server or import an OpenAPI spec. Riley uses your tools inside the same rules.
The surface changes. The rule does not. No matter where you connect from, the approval gate is the same.
Work you start from Claude, ChatGPT, Slack, or any other client is not a black box. Actions taken through any surface appear in your approvals queue and receipts, exactly like work done from the dashboard. One place to approve, one place to prove.
In the Riley dashboard first, then in Claude Desktop, Claude Code, and Cursor over MCP, in ChatGPT where your plan supports custom MCP connectors, in Slack, and in any other MCP-compatible client with guided setup. Microsoft Teams and email are in beta.
No. Sign in at app.hireriley.com, mint a key in Settings, and paste it into your AI tool where it asks for a custom MCP server. The dashboard and Slack need no key at all.
Sign in at app.hireriley.com and mint a per-workspace key in Settings. The key is shown once and can be revoked any time. Send it as the x-api-key header, or use Authorization: Bearer.
No. Whatever surface you connect from, anything that posts or changes something external waits for your approval. Reading and drafting happen freely; external writes queue for your yes.
Every action taken through any surface appears in your approvals queue and receipts, exactly like work done from the dashboard.
Create a free workspace, mint a key, and bring Riley into the tools you already use. No card to begin.