What is Tiro MCP Server?
Tiro MCP Server is a hosted service that enables AI agents (Claude, GPT, etc.) to access your meeting notes from Tiro AI Note Taker through the Model Context Protocol (MCP).Key Features
Progressive Disclosure Pattern Minimize token usage by loading data incrementally—metadata first, details only when needed. This approach reduces token consumption by up to 85%. OAuth 2.0 Authentication Industry-standard OAuth 2.0 with JWT tokens provides secure, scoped access to your meeting data. Hosted Service No local installation required. Connect directly tohttps://mcp.tiro.ooo/mcp and start using immediately.
Four Core Tools
search_notes- Search meetings by content, date, or participantsget_note_transcript- Retrieve full conversation transcriptsget_note_summary- Get AI-generated meeting summariesget_note_documents- Extract structured data (action items, decisions)
Quick Start
Get up and running in 2 steps:1
Configure Your Client
Add Tiro MCP Server to your preferred client (Claude Code or Claude Desktop).See Authentication for detailed configuration instructions.
2
Authenticate via Browser
When you first connect to Tiro MCP Server:
- Your client will automatically open a browser for authentication
- Sign in with your Google account (or create a Tiro account if you don’t have one)
- Complete the OAuth flow
- Return to your client - you’re now connected!
Progressive Disclosure Architecture
Tiro MCP Server uses a three-stage pattern to optimize token usage:Stage 1: Metadata
search_notes~50 tokens per noteReturns only titles, dates, and participant names
Stage 2: Summary
get_note_summary~200-800 tokensAI-generated condensed summary of the meeting
Stage 3: Full Content
get_note_transcript~3,000-5,000 tokensComplete conversation transcription
Compatible Clients
Tiro MCP Server works with any MCP-compatible client:- Claude Desktop - Official Anthropic client
- Claude Code - CLI tool for developers
- Continue - VS Code extension
- Cursor - AI-powered IDE
- Cline - Terminal-based client
- Any other MCP-compatible application
Limitations
Current Limitations:- Maximum 50 notes per search (pagination not yet supported)
- Request timeout: 60 seconds
- Single scope:
mcp:notes:read(additional scopes planned) - Response times vary with transcript length (~2-3 seconds for 1-hour meetings)
Security & Privacy
- All communication uses HTTPS and OAuth 2.0
- Tokens expire automatically based on your configuration
- No sensitive data is logged or stored by the MCP server
- Read-only access prevents accidental data modification

