The Tiro MCP server lives atDocumentation Index
Fetch the complete documentation index at: https://api-docs.tiro.ooo/llms.txt
Use this file to discover all available pages before exploring further.
https://mcp.tiro.ooo/mcp. Pick the client you use, follow the steps, and you’re connected. Each client has a recommended authentication method, and most support an alternative.
Don’t have an API key yet? Create one at the Tiro Platform API Keys page. Your key looks like
abc123.xR7mK9pL2qW4... — copy the entire string including the dot. The dashboard shows a “Key ID” (e.g., abc123) for reference, but your Bearer token is the complete string shown only once at creation. If lost, generate a new one.Scopes
Scopes define what the MCP server can access on your behalf. API keys currently grant all scopes automatically.| Scope | Description |
|---|---|
mcp:notes:read | Read notes, transcripts, summaries, documents, and templates |
mcp:notes:write | Manage share links |
mcp:folders:read | Read user and team folder structure |
mcp:folders:write | Create, update, delete, and move team folders |
mcp:voice:read | Read voice file job status, transcripts, and translations |
mcp:voice:write | Create voice file jobs (planned) |
Granular scope selection is not yet available. All authenticated connections receive full access. Fine-grained scope control is planned for a future release.
API key types
| Key Type | Created By | Access |
|---|---|---|
| Personal API Key | Any user | Your own notes, summaries, documents, personal folders |
| Team API Key | Team admin | Team folders, team-shared notes |
Which key do you need? Most users start with a personal API key. You can search and read all notes you have access to, including notes in team folders. A team API key is only needed when you want to manage team folder structure (create, move, delete folders).