API & MCP.

Reever's MCP server lives at https://www.reever.ai/api/mcp and speaks the Streamable HTTP transport. Authentication is OAuth 2.1 with PKCE + Dynamic Client Registration; legacy bearer keys (rvr_live_*) are also accepted for headless scripts.

Claude Desktop / Cursor:add the server in settings using OAuth — point your client at the URL above and it'll discover the authorization server automatically and walk you through consent.

{
  "mcpServers": {
    "reever": {
      "url": "https://www.reever.ai/api/mcp"
    }
  }
}

On first connect the client opens a browser tab to /oauth/authorize, you sign in (or are already signed in), approve the consent screen, and the client is issued an access + refresh token. No copy/paste of secrets.

Headless setup (scripts, n8n, Zapier)

For non-AI integrations where running an OAuth dance is overkill, generate a personal API key at Settings → Developer and pass it as a Bearer token. Same MCP endpoint, same tool surface — just a different auth path.

{
  "mcpServers": {
    "reever": {
      "url": "https://www.reever.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer rvr_live_..."
      }
    }
  }
}

OAuth 2.1 (recommended for AI clients)

Standards-compliant flow per the MCP authorization spec: Authorization Code with PKCE (S256), refresh tokens, Dynamic Client Registration. Discovery via /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.

• ·POST /oauth/register — RFC 7591 DCR. Open registration, no initial access token required. Returns a client_id (and client_secret for confidential clients).
• ·GET /oauth/authorize — user consent UI. Required params: response_type=code, client_id, redirect_uri, code_challenge (S256),code_challenge_method=S256, scope, state.
• ·POST /oauth/token — exchange auth code for tokens (grant_type=authorization_code) or refresh (grant_type=refresh_token). Refresh tokens rotate on every use.
• ·POST /oauth/revoke — RFC 7009 revocation.

Access tokens are bound to the resource https://www.reever.ai/api/mcp (audience-binding per the MCP spec). Default lifetime: 1 hour for access tokens, 30 days for refresh tokens. Single supported scope today: reever:rw.

Personal API keys (headless / scripts)

Generate at Settings → Developer. Keys begin with rvr_live_ and are shown once at creation — copy immediately. Pass as bearer token or custom header:

Authorization: Bearer rvr_live_xxxxxxxxxxxxxxxxxxxxxxxx
# or
X-Reever-Api-Key: rvr_live_xxxxxxxxxxxxxxxxxxxxxxxx

Personal keys are Pro-tier. OAuth is available on every plan. Both flows give equivalent access — same MCP tool surface, same REST endpoints.

Six tools are live today. Annotations follow the MCP tool annotation spec so AI clients can decide whether to prompt before invoking.

Base URL: https://www.reever.ai. Versioned under /api/v1/. Bearer-key auth identical to MCP.

curl https://www.reever.ai/api/v1/event-types \
  -H "Authorization: Bearer rvr_live_..."

{
  "eventTypes": [
    {
      "id": "01HX...",
      "slug": "30min",
      "title": "30-minute intro",
      "durationMins": 30,
      "isActive": true,
      "createdAt": "2026-04-12T15:30:00.000Z"
    }
  ]
}

REST coverage is intentionally narrow — the full surface lives on MCP. If you need a specific endpoint that isn't here, email eli@ventechdigital.com.