Available tools
The server exposes four read tools, each wrapping an endpoint of the v1 REST API. All of them are read-only and scoped to the connected workspace. The usual path is to list conversations, then open the one you want.
list-conversations GET /api/v1/conversations List conversations (transcribed meetings and notebooks), newest first. Returns metadata and the source list, not full transcript content. Use get-conversation to read content.
| limit | number | Max items, 1–100. Defaults to 25. |
| cursor | string | Pagination cursor from a previous response. |
| folder_id | string | Restrict to a single folder. |
| recursive | boolean | Include sub-folders. Defaults to true. |
| status | enum | ready, pending, error, or all. Defaults to ready. |
| created_after | string | ISO 8601 timestamp lower bound. |
get-conversation GET /api/v1/conversations/{id} Retrieve one conversation in full: its AI summary and every source with full transcript text and participants.
| id required | string | Conversation id, from list-conversations. |
list-folders GET /api/v1/folders List folders the current user can see. Folder ids can be passed as the folder_id filter on list-conversations.
| limit | number | Max items, 1–100. |
| cursor | string | Pagination cursor from a previous response. |
| folder_id | string | Restrict to a single parent folder. |
| recursive | boolean | Include sub-folders. |
get-me GET /api/v1/me Return the email and workspace name the current connection is bound to. Useful for confirming which Klang account a client is connected as.
No parameters.
What's not exposed
Anything that creates or changes data is left off MCP on purpose. Creating recorder bots (POST /api/v1/bots) and every other write operation go through the REST API with an API key instead.