Developers

Riley MCP and API.

one endpoint · per-workspace keys · approval-gated writes

Connect Riley over MCP and bring your own tools. 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.

Endpoint

One endpoint, one header.

MCP endpoint (Streamable HTTP)

https://app.hireriley.com/mcp

Auth header

x-api-key: YOUR_RILEY_KEY

Authentication is a per-workspace key minted in Settings 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.

Tools

The tools your key can call.

riley_audit

Run a read-only audit of a connected surface and return what it found.

riley_respond

Draft a reply to a review or message. The draft waits for your approval before anything is sent.

riley_social

Draft a social post in your brand voice. Publishing waits for your approval.

riley_prospect

Find and log leads into your workspace so nothing slips through.

riley_memory

Read and write your workspace memory: brand voice, preferences, and things never to mention.

riley_health

Check the health of your workspace and its connections.

Example

Listing the tools your key can call.

Request

POST https://app.hireriley.com/mcp
x-api-key: YOUR_RILEY_KEY
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Response

{
  "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": "..." }
    ]
  }
}

Supported methods

initialize
Handshake and capability negotiation when a client connects.
tools/list
Return the tools your key can call, with their input schemas.
tools/call
Invoke a tool. Writes that reach outside your workspace queue for approval before they run.

Not supported yet

Server-sent events (SSE) streaming. The endpoint is Streamable HTTP; there is no long-lived SSE transport yet.
MCP resources and prompts. Only tools are exposed today.
OAuth. Authentication is a per-workspace key sent as a header, not an OAuth flow.

Bring your own tools

Give Riley your own tools.

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 reaches outside your workspace only through an approval. An OpenAPI import turns each documented operation into a callable tool.

Fair use

Reasonable use.

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.