Connect your client

The Tiro MCP server address is https://mcp.tiro.ooo/mcp. Find the setup steps for your client below.

No API key yet? Create one at the Tiro Platform API Keys page. Copy the entire string including the dot, like abc123.xR7mK9pL2qW4.... The full key is shown only once, at creation.

Claude (web browser)

If you use claude.ai in a browser, connect through a remote connector — no installs. OAuth only (there is no API key field).

Open claude.ai/customize/connectors, go to Connectors → Discover, and search for Tiro.
On the Tiro card (Community, by ThePlato Inc.), click Connect Tiro to Claude.
Sign in with your Tiro account and allow the permissions. After connecting, each tool call asks for approval by default (switch individual tools to Always allow in the connector settings).

The Add custom connector path with the server URL (https://mcp.tiro.ooo/mcp) still works too.A step-by-step walkthrough for non-developers lives in the user guide.

Claude Desktop

Recommended: OAuth. Sign in once, the client manages tokens.

Node.js is required. The mcp-remote package bridges streamable-http to the stdio transport that Claude Desktop expects.

Open the configuration file for your platform:

~/Library/Application Support/Claude/claude_desktop_config.json

%APPDATA%\Claude\claude_desktop_config.json

~/.config/Claude/claude_desktop_config.json

Add the OAuth configuration:

claude_desktop_config.json

{
  "mcpServers": {
    "tiro": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.tiro.ooo/mcp"]
    }
  }
}

Restart Claude Desktop. On first connection, your browser opens for Google sign-in, then the Tiro consent screen where you pick the permissions to grant with per-scope checkboxes (read scopes are selected by default, write scopes are off; selecting write includes read for the same resource). Tokens are cached locally and valid for 180 days.Alternative: API Key. If you prefer no browser flow, use:

claude_desktop_config.json

{
  "mcpServers": {
    "tiro": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.tiro.ooo/mcp",
        "--header", "Authorization:Bearer YOUR_API_KEY"
      ]
    }
  }
}

Claude Code (CLI)

Recommended: API Key. Avoids browser dependency, easy to rotate.

claude mcp add --transport http tiro-mcp https://mcp.tiro.ooo/mcp \
  --header "Authorization:Bearer YOUR_API_KEY"

Alternative: OAuth. Omit --header. Claude Code opens a browser on first connection.

claude mcp add --transport http tiro-mcp https://mcp.tiro.ooo/mcp

ChatGPT

Since the July 2026 revamp, ChatGPT handles external connections through its apps and plugins system. Custom MCP servers that aren’t in the plugin directory (including Tiro) can only be connected in developer mode.Web only (no mobile). Personal accounts need the Pro plan or higher (read/fetch scope). On Business only admins/owners can use developer mode; on Enterprise/Edu, members granted access via RBAC.

Go to Settings → Plugins → Developer mode at the bottom of the list, then turn on the Developer mode toggle in the security settings.
On the sidebar Plugins page, click [+] → New Plugin, enter a name plus the server URL https://mcp.tiro.ooo/mcp, acknowledge the risk notice, and click Create.
Sign in with Tiro → sign in to your Tiro account → on the permission screen check Long-lived access (ChatGPT requires refresh, and the allow button only activates once checked) → Allow selected access.
Select the app from the tools menu in a chat. Selection applies per message. (UI verified live 2026-09-11)

For detailed requirements and workspace publishing, see the official OpenAI guide. The UI is in beta and may change.

Codex (CLI)

Recommended: API key. Codex is stdio-based, so wrap the endpoint with mcp-remote. Add this to ~/.codex/config.toml.

~/.codex/config.toml

[mcp_servers.tiro]
command = "npx"
args = [
  "-y", "mcp-remote",
  "https://mcp.tiro.ooo/mcp",
  "--header", "Authorization:Bearer YOUR_API_KEY"
]

Alternative: OAuth. Remove the two --header lines and a browser opens on first connection.

Cursor

Recommended: API Key.

Open Settings > MCP.
Click Add new MCP server.
Set transport to HTTP.
Enter the server URL: https://mcp.tiro.ooo/mcp.
Add a header: Authorization: Bearer YOUR_API_KEY.

VS Code (Copilot)

Recommended: API Key. Create or edit .vscode/mcp.json in your workspace:

.vscode/mcp.json

{
  "servers": {
    "tiro": {
      "type": "http",
      "url": "https://mcp.tiro.ooo/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Other MCP clients

Any MCP client that speaks streamable-http works with these raw values:

Field	Value
Server URL	`https://mcp.tiro.ooo/mcp`
Transport	HTTP (streamable)
Auth header	`Authorization: Bearer YOUR_API_KEY`
OAuth issuer	`https://mcp.tiro.ooo` (if your client supports OAuth 2.0 with PKCE)

For stdio-only clients, wrap the endpoint with mcp-remote:

npx -y mcp-remote https://mcp.tiro.ooo/mcp \
  --header "Authorization:Bearer YOUR_API_KEY"

Scopes

Scopes define what the MCP server can access on your behalf. MCP scopes share the REST API scope vocabulary with an mcp: prefix. When a client discovers tools, it sees only those allowed by the scopes selected for the connection.

Scope	Description
`mcp:note:read`	Read note metadata, AI summaries, transcripts, generated documents, share links, document templates, and the wiki — the wiki and template tools are gated by this single scope, with no separate scope
`mcp:folder:read`	Search user and workspace folder structure
`mcp:note:write`*	Update note titles
`mcp:folder:write`*	Update, move, and reorder folders

* No MCP tool currently maps to this scope (REST API only — all MCP tools are read-only).

API keys: the scopes configured on the key apply as-is. On the API Keys page you pick the REST names without the mcp: prefix (note:read, folder:write, …) — the prefix only appears on MCP surfaces such as auth_status. Keys without scopes can use every tool, and write scopes include their read counterpart.
OAuth: when connecting, the Tiro consent screen lets you choose None or Read for Notes and Folders. The MCP OAuth flow doesn’t request the write scopes (mcp:notes:write, mcp:folders:write) — see the * note in the table above, no MCP tool maps to them — so a Read & edit level never appears. Your selection is fixed into the token.

Existing tokens and keys issued with the legacy names (mcp:notes:read, mcp:folders:read) keep working.

API key types

Key Kind	Tied To	Access
User-scoped key	A user	Every note, summary, document, and folder that user can access — can span multiple workspaces
Workspace-scoped key	One workspace	Notes in folders shared with all members of that workspace; no user identity

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 workspace 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 API 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 credentials with user identity (a user-scoped API key or OAuth token) and the mcp:folder:read scope.

API keys do not expire unless revoked from the Tiro Platform API Keys page. We recommend rotating keys periodically and using separate keys for development and production. OAuth tokens are valid for 180 days. To rotate sooner, sign out from your client and sign in again. For immediate revocation, contact support. Once connected, explore what tools are available — or head to Troubleshooting if your client isn’t connecting.

Home

Getting Started

API

Voice File

Webhooks

MCP

CLI

Developer Resources

Connect your client

Scopes

API key types

​Scopes

​API key types

Scopes

API key types