> ## Documentation Index
> Fetch the complete documentation index at: https://docs.risos.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to RISOS MCP

> Connect a header-capable MCP client with a least-privilege RISOS API key.

RISOS product MCP uses scoped, Workspace-specific API keys for production authentication.

**Endpoint:** `https://risos.co/api/mcp`

Send the key as:

```text theme={null}
Authorization: Bearer $RISOS_API_KEY
```

Every session requires `mcp:use`. Add only the capability scopes the client needs:

* read Product judgments, Ask, Explore, Signals, or Research state: `research:read`
* start or refresh Research and create Reports: `research:write`
* read Evidence or Entities: `evidence:read`
* read Monitors: `monitor:read`
* create/update Monitors: `monitor:write`

A read-only research client therefore typically uses `mcp:use` + `research:read`.

RISOS does not currently advertise the MCP OAuth 2.1 authorization profile. Use dedicated revocable API keys, one key per client when practical, and rotate them independently.