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.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
Which key do you need? Most users start with a user-scoped key — you can search and read all notes you have access to, including notes in team folders, across every workspace you belong to. A workspace-scoped key searches only the workspace it is connected to, and inside that workspace it reads only notes in folders shared with all members (What notes a system key reads). Use a user-scoped key if you need notes in private folders. MCP tools use the same keys and follow the same read scope rules as the REST API. The folder tools (
search_private_folders, search_team_folders) require the mcp:folders:read scope.