Install Tiro MCP in your agent

Copy this prompt

The Tiro MCP install prompt

Install the Tiro MCP server in this workspace.

  Server URL :  https://mcp.tiro.ooo/mcp
  Transport  :  HTTP (streamable)
  Auth       :  OAuth (preferred). On first connection, open a browser
                for Google sign-in. Tokens cache locally for 180 days.

If this client cannot run a browser flow, ask me for a Tiro API key
from https://platform.tiro.ooo/dashboard/api-keys and attach the
header:

  Authorization: Bearer <TIRO_API_KEY>

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

  npx -y mcp-remote https://mcp.tiro.ooo/mcp

After connecting, list the Tiro tools that loaded and call
`auth_status` to confirm the session is live. If a step fails, show
me the exact error and the step where it happened — do not retry
silently.

The prompt is intentionally client-agnostic. Your agent picks the right config file (claude_desktop_config.json, .vscode/mcp.json, Cursor settings, etc.) based on where it’s running.

What your agent will do

Detect the active MCP client and open its config.

Add a tiro server entry pointing at https://mcp.tiro.ooo/mcp.

Restart the client (or prompt you to) and complete OAuth in your browser.

Call auth_status to verify the connection and report which tools are available.

If anything fails, the agent surfaces the exact error so you know which step to retry — no silent loops.

Privacy & token handling

OAuth tokens are cached in your local MCP client config only — never sent anywhere else.

API keys (if used as fallback) are stored in plain text inside that same config file; keep it out of shared dotfiles.

Revoke either at any time from the API Keys dashboard or by signing out from your client.

​Copy this prompt

​What your agent will do

​Privacy & token handling

Copy this prompt

What your agent will do

Privacy & token handling