MeetGeek
MeetGeek MCP Server provides programmatic access to MeetGeek.ai’s meeting intelligence capabilities through a structured API interface. Built on top of the official MeetGeek API, it enables developers and organizations to integrate meeting data and AI-generated insights directly into their internal tools, workflows, and applications. MeetGeek.ai is an AI-powered meeting assistant that records, transcribes, and analyzes meetings across major conferencing platforms, turning conversations into searchable, actionable knowledge. This server exposes core MeetGeek features such as meeting management, detailed metadata, full transcripts, summaries, highlights, insights, team-level views, and recording uploads, allowing teams to automate post-meeting workflows and extend MeetGeek’s value beyond its native interface. Designed for self-hosting and secure operation, the server uses a user-provided MeetGeek API key and provides a reliable way to embed MeetGeek’s meeting intelligence into enterprise systems, automation pipelines, and AI-driven products.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Pending
- Secondary Subcategories
- Meeting Notes & Call Intelligence
- Brand
- MeetGeek
- Access
- Unknown
- First tracked
- 2026-04-15
- Tool count
- 8
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is visible.
Claude Discoverability Score
Your public score is being prepared
MeetGeek is tracked in the public registry. Its Discoverability Score will appear as soon as the public benchmark is ready - never as an estimate.
Competitive lineup
How the Discoverability Score works
The Claude Discoverability Score will be the percentage of contested conversations where MeetGeek appears in the connector picker or Claude invokes it directly. Found and Positioned will be shown as diagnostics, not score inputs.
Organic discovery scoring is pending. Your Connector score will appear on this scale when measurement goes live.
FoundDiagnostic
Whether Claude found your Connector in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.
PickedMain score
How often your Connector appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.
PositionedDiagnostic
What position your Connector appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.
8 tools agents can invoke
How do I improve a Verified 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.