Build with AI

The Dwrrah MCP server exposes the same capabilities as the REST API — as tools for AI agents — under the same scopes and the same single-academy isolation. Read tools mirror the GET endpoints; write tools are guarded (drafts / explicit confirm) and idempotent.

Server URL: https://mcp.dwrrah.com

🔒
Every tool runs under the scopes of the connection. payments, hard deletes, and AI execution are not exposed as tools.

Two ways to connect

API key (Bearer)

For clients that support a bearer token — send Authorization: Bearer dwr_live_…. The academy and scopes are derived from the key.

OAuth 2.1 (PKCE)

For connector-style clients — add the server URL as a connector, approve one academy and its scopes on the consent screen, and the token is bound to that academy.

API key

Create an MCP-enabled key in your dashboard, then point your MCP client at the server with the key as a bearer token. The academy and its scopes come from the key — you never pass an academy_id.

OAuth

Add https://mcp.dwrrah.com as a connector in a client that supports OAuth connectors. You'll be sent to a Dwrrah consent screen to pick one academy and approve scopes. Connections can be reviewed and revoked from your dashboard at any time.