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

# Overview

> Connect AI clients to Rookoo through the portal Model Context Protocol server.

The Rookoo portal ships an [MCP](https://modelcontextprotocol.io/) server. AI clients (Claude Desktop, Cursor, Copilot, custom agents) can call Rookoo tools and read resources over Streamable HTTP.

## Endpoints

| Endpoint | Scope |
| - | - |
| `POST /api/v1/accounts/{account_id}/mcp` | Preferred. Tools and resources for one account, filtered by membership and permissions. |
| `POST /api/v1/mcp` | Global entrypoint. Tools resolve accounts from tool arguments. |

Base URL:

```
https://app.rookoo.ai
```

Account-scoped URL example:

```
https://app.rookoo.ai/api/v1/accounts/1/mcp
```

## What you can do

The server exposes tools for:

* Inboxes, contacts, conversations, and messages
* Planning events, spaces, allocations, and quotes
* Pricing plans, rates, and rules
* Knowledge bases and records
* Rookoo AI agents, instructions, facts, and procedures
* Labels, teams, companies, canned responses, and automations
* Analytics and CSAT

See [Tools](/mcp/tools) and [Resources](/mcp/resources).

## Transport

The portal uses MCP Streamable HTTP with JSON responses. Send JSON-RPC MCP messages in the request body. The server responds with MCP result payloads.

Discovery endpoints for OAuth clients:

* `GET /.well-known/oauth-protected-resource`
* `GET /.well-known/oauth-authorization-server`
* `GET /.well-known/jwks.json`

## Not included

Enterprise-only Chatwoot surfaces are not exposed through this MCP server or the published REST docs. That includes audit logs, SLA policies, Captain enterprise routes, SAML settings, agent capacity policies, voice conference, and similar enterprise controllers.