Tiro
Search meetings, notes, and wiki from Claude
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Tiro is the meeting notetaker for teams that work in more than one language. It records a conversation, writes a transcript in real time, and turns that transcript into a structured note plus a wiki your company can search later. Connect Tiro to Claude when the user asks what happened in a meeting, what was decided, who owns an action item, or what a customer said last week. Claude can search notes, open a transcript, read a summary, list folders, and look up a note's share link. Claude cannot see notes the user cannot see in the Tiro app. Tiro is strongest on Korean, Japanese, and mixed-language rooms. Original recordings stay on the user's device. Any Tiro plan can connect. The default sign-in is OAuth with the same account used in the Tiro app. An API key is available for headless or CI setups. Start with: "Summarize this week's meetings and list open action items."
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- No account required
- First tracked
- 2026-09-08
- Tool count
- 16
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
16 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.