Connect any client that speaks the Model Context Protocol to your Riley workspace: one endpoint, per-workspace keys, a small set of scoped tools, and approvals on anything that writes outside your workspace.
one endpoint · per-workspace keys · approval-gated writes
Start freehttps://app.hireriley.com/mcp
x-api-key: YOUR_RILEY_KEY
Authentication is a per-workspace key minted in the app and sent as the x-api-key header (keys start with rmcp_). Keys are shown once at mint, stored only as a hash, and revocable at any time. Riley cannot show a key again after minting, so keep it somewhere safe or revoke and mint a new one. Authorization: Bearer works as well.
Run a read-only audit of a connected surface and return what it found.
Draft a reply to a review or message. The draft waits for your approval before anything is sent.
Draft a social post in your brand voice. Publishing waits for your approval.
Find and log leads into your workspace so nothing slips through.
Read and write your workspace memory: brand voice, preferences, and things never to mention.
Check the health of your workspace and its connections.
POST https://app.hireriley.com/mcp
x-api-key: YOUR_RILEY_KEY
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"tools": [
{ "name": "riley_audit", "description": "..." },
{ "name": "riley_respond", "description": "..." },
{ "name": "riley_social", "description": "..." },
{ "name": "riley_prospect", "description": "..." },
{ "name": "riley_memory", "description": "..." },
{ "name": "riley_health", "description": "..." }
]
}
}
initializetools/listtools/callEvery Riley tool falls into one of four categories. Read and draft freely; anything that writes outside your workspace queues for approval. Riley never exposes raw keys or secrets, and it never performs unscoped writes.
Audits and health checks read connected surfaces and return what they found. Nothing changes.
Replies, posts, and follow-ups are drafted in your voice and held until you decide.
Any write that reaches outside your workspace waits in the approvals queue, whatever client asked for it.
Completed work lands in the ledger and signed receipts, so a client or manager can check it.
Beyond the built-in tools, you can register your own MCP server or import an OpenAPI spec from the AI Access section of your dashboard. Riley then uses those tools under the same rules: they are workspace-scoped, revocable, and any write that reaches outside your workspace only happens through an approval. An OpenAPI import turns each documented operation into a callable tool.
The MCP endpoint is for working with your own Riley workspace, not for reselling raw access or hammering it with automated traffic. Requests may be rate limited to keep the service healthy for everyone; if you have a high-volume need, talk to us and we will scope it with you rather than guess at a number here.