Thor.ai
The context layer that ensures your agents know your team’s latest decisions, scope changes, and discussions, before they start their work.
- Category
- Pending
- Primary Subcategory
- Pending
View in the Claude registryIntegration details
Description
Thor connects Claude to the tools your team uses, infers projects, decisions, and commitments, and enriches everything your agents do with up to date context. This gives Claude a single MCP connection to let it efficiently pull the latest data from your team and ensure everyone's in sync. Use Thor to: * Help Claude get the freshest picture of your team's decisions before doing its work * Create high-quality issues, check for duplicates automatically, and link to supporting work * Extract action items, decisions, and commitments from meeting transcripts Thor can connect to: * Issues in GitHub and Linear * Team chats in Slack and Microsoft Teams * Meetings in Google Meet, Zoom, and Teams * Documents in Notion
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-09-22
- Tool count
- 19
- 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
19 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.