Overview
Tiro MCP Server uses OAuth 2.0 Authorization Code with PKCE and JWT tokens (HS256 algorithm) to provide secure, scoped access to your meeting notes. Authentication is handled through Google OAuth login. Your MCP client (Claude Code or Claude Desktop) automatically initiates the OAuth flow on first connection. After signing in with Google, a JWT access token is issued withmcp:notes:read scope and is valid for 180 days.
Currently, Tiro supports Google OAuth login only. Support for email/password login and Microsoft OAuth is planned for future releases.
Claude Code Setup
Claude Code is Anthropic’s official CLI tool that supports MCP servers with OAuth authentication natively. On first connection, Claude Code will automatically open your browser for Google OAuth sign-in.Claude Desktop Setup
Claude Desktop connects to Tiro MCP Server using themcp-remote proxy, which translates the streamable-http protocol into the stdio transport that Claude Desktop supports.
Prerequisites: Node.js must be installed. Verify that the
npx command works in your terminal.Configuration File Location
Setup Steps
Add Tiro MCP Server
Open the configuration file and add:If you already have other MCP servers configured, add the
claude_desktop_config.json
tiro entry inside the existing mcpServers object.Restart Claude Desktop
Quit Claude Desktop completely and relaunch it (not just a window refresh — fully quit and restart).
Authenticate
On first connection, your browser will open for Google OAuth sign-in. After authentication, tokens are cached locally and Claude Desktop will reconnect automatically on future restarts.
Token Expiration
Tokens are valid for 180 days. When a token expires, your MCP client will automatically trigger the OAuth flow again — just sign in with Google and you’re reconnected.Next Steps
Explore Tools
Learn about the four available MCP tools
Troubleshooting
Solutions for common issues

