Riley dashboard
LiveThe full product in your browser, no setup beyond signing in.
Setup guideUse Riley anywhere
one workspace · every client · same approval gate
Work with Riley from the tools and channels you already use. One Riley workspace behind every surface: your memory, permissions, approvals, verification, and proof stay in one place, no matter which client asks for the work.
Connect in three steps
Use MCP to let supported AI clients and agents request Riley work through your approval rules. Your key stays yours, and every external write still waits for approval.
Sign in, open Settings, and create a key. Riley shows it once, so copy it somewhere safe.
https://app.hireriley.comIn Claude Desktop, open Settings, Developer, Edit config, add Riley as an MCP server, then restart.
https://app.hireriley.com/mcpAsk for work in plain language. Riley drafts, and anything that writes outside your workspace waits for your approval.
Ask Riley to audit my Google Business ProfileSupported clients
Every status below comes from our live support config, not from marketing. If a client is not verified, the card says so.
Surfaces we document end to end.
The full product in your browser, no setup beyond signing in.
Setup guideThe raw MCP endpoint for anything that speaks the protocol, with per-workspace keys.
Setup guideVerified: connect Riley as an MCP server and work from Claude Desktop.
Setup guideVerified: add Riley with one command and use it from the terminal.
Setup guideVerified: add Riley as an MCP server in Cursor settings.
Setup guideUse Riley from ChatGPT through supported MCP/custom app setup. Riley permissions and approval rules still apply.
Setup guideOptional delivery channel: receipts, approval requests, and alerts can land in Slack. It is also a data source Riley can read and analyze.
Setup guideReal today, with the caveat stated honestly on each card.
Beta: Riley in Teams is in testing and needs setup with our team.
Setup guideMCP compatible with guided setup; we have not individually verified this client.
Setup guideMCP compatible with guided setup; we have not individually verified this client.
Setup guideMCP compatible with guided setup; we have not individually verified this client.
Setup guideMCP compatible with guided setup; we have not individually verified this client.
Setup guideMCP compatible with guided setup; we have not individually verified this client.
Setup guideMCP compatible with guided setup; we have not individually verified this client.
Setup guideMCP compatible with guided setup; we have not individually verified this client.
Setup guideAny client that speaks MCP, plus your own tools.
Any client that speaks MCP can connect: Open WebUI, LM Studio, LibreChat, MCPJam, VS Code, Replit, Devin, internal agents, and more. Not individually verified.
Bring your own MCP server or import an OpenAPI spec; Riley uses your tools inside the same rules.
Approval gate
Reading and drafting are free to happen on any surface. Anything that changes something outside your workspace waits in your approvals queue first, no matter which AI client asked for it. Riley will not, without approval:
Every action taken through any surface appears in your approvals queue and your proof receipts, like any other Riley work. No surface gets a side door.
FAQ
MCP (Model Context Protocol) is an open standard that lets AI tools like Claude, ChatGPT, and Cursor call other services as tools. Riley exposes an MCP endpoint, so the AI tools you already use can ask Riley to do work while your memory, permissions, approvals, and proof stay in one Riley workspace.
Keys are shown once when you create them, stored only as a hash, and revocable in Settings at any time. Riley cannot show you a key again after minting. If you lose one, revoke it and mint a new one.
Claude Desktop, Claude Code, and Cursor are verified end to end. ChatGPT works where your ChatGPT plan supports custom MCP connectors. Several more MCP compatible clients have guided setup, and any client that speaks MCP can connect to the same endpoint.