Hedy's Model Context Protocol (MCP) integration connects your meeting intelligence directly to AI assistants like Claude. Access sessions, organize topics, and work with meeting data through natural language—18 specialized tools make your conversation history a queryable knowledge base.

Hedy's MCP integration lets AI assistants create topics, manage contexts, and organize your meeting data. Connect Claude or other AI tools to your AI meeting assistant with 18 available tools and enhanced API capabilities.
Starting today, Hedy connects directly with Claude and other AI assistants through the Model Context Protocol (MCP). This means your AI tools can now access, organize, and work with your meeting data without you manually copying information between applications.
The MCP server gives AI assistants like Claude Desktop direct access to your Hedy data through 18 specialized tools. Here's what becomes possible:
Session Management
AI assistants can retrieve your meeting transcripts, summaries, and insights. Ask Claude to "find the budget discussion from last week's client meeting" and it pulls the exact session with full context.
Topic Organization
Create and manage topics programmatically. Your AI can automatically organize related meetings, build knowledge bases from conversation series, and track project evolution across multiple sessions.
Highlight Capture
Access saved highlights with their AI-generated analysis. Build study guides from lecture highlights, compile decision points from business meetings, or extract key quotes from interviews.
Task Integration
Pull to-do items directly into your workflow. AI assistants can aggregate action items across projects, identify overdue tasks, or create consolidated task lists from multiple meetings.
The MCP server runs at https://api.hedy.bot/mcp and authenticates using your Hedy API key. Configuration takes about two minutes:
The integration supports both session-level queries ("What did we discuss about pricing?") and cross-session analysis ("Show me all action items from client meetings this month").
The MCP integration maintains Hedy's privacy-first design. Data remains encrypted in transit and at rest. The MCP server provides read access to your meeting data—AI assistants can retrieve and analyze information but cannot modify your original sessions or transcripts.
Authentication is user-specific. Only AI tools configured with your API key can access your data. Keys can be revoked instantly through Account Settings if needed.
The MCP server provides 18 specialized tools organized by function:
Session Access
Topic Management
Highlights & Tasks
Research Analysis
Academics use the integration to synthesize findings across lecture series. Ask Claude to "compare the three theoretical frameworks discussed in weeks 4-6" and it pulls relevant content from multiple sessions, cross-references concepts, and generates comparative analysis.
Client Management
Consultants maintain comprehensive client histories. The AI can "prepare for tomorrow's meeting with [Client] by reviewing all previous discussions about their Q4 strategy" and generates a briefing document with relevant context, outstanding commitments, and suggested talking points.
Knowledge Management
Teams build institutional knowledge. The MCP integration lets AI assistants create structured documentation from meeting series, extract best practices from retrospectives, and compile technical specifications from design discussions.
Workflow Automation
Developers integrate Hedy data into custom systems. Combine MCP access with n8n or Make.com to build automated workflows that route meeting insights to project management tools, update CRMs, or trigger follow-up actions.
The MCP integration works with any MCP-compatible client. Confirmed compatible applications include:
A Hedy Pro subscription provides full API access required for MCP integration. Free tier users have limited API access suitable for testing but not production workflows.
Complete setup instructions are available in Hedy's help documentation. The configuration process involves generating an API key, adding the MCP server to your AI client, and testing the connection with a simple query.
For developers building custom integrations, API documentation covers authentication methods, rate limits, and response schemas. The MCP server supports standard MCP protocol features including tool discovery and capability negotiation.
The MCP integration transforms how professionals use meeting intelligence. Instead of manually searching through past sessions or copying information into documents, AI assistants handle the heavy lifting—finding relevant context, synthesizing information across conversations, and presenting actionable insights.
This matters because professional work increasingly happens through conversations. The knowledge captured in meetings, calls, and discussions represents significant organizational intelligence. The MCP integration makes that intelligence accessible to the AI tools you already use for analysis, writing, and decision-making.
For organizations, this means meeting data becomes a queryable knowledge base. For individuals, it means every conversation you've had with Hedy becomes available to assist with current work—no manual organization required.
The implementation follows MCP specification version 1.0, ensuring compatibility with the growing ecosystem of MCP-enabled applications. The server architecture supports concurrent requests, implements efficient caching for frequently accessed data, and includes automatic retry logic for transient failures.
Response times typically range from 100-500ms for session retrieval and 200-1000ms for complex cross-session queries, depending on data volume and analysis depth.
The current implementation provides comprehensive read access to Hedy data. Future updates will add write capabilities, enabling AI assistants to create highlights during analysis, add custom tags to sessions, and append notes to meetings programmatically.
Integration with additional protocols beyond MCP is under evaluation based on ecosystem adoption and user requests.
Documentation is available in Hedy's help center, including setup guides for popular AI clients, troubleshooting common configuration issues, and example queries for different use cases.
The Hedy Slack community includes an #mcp-integration channel where users share configurations, discuss workflows, and provide mutual support for technical implementation questions.
The MCP integration is available now for Hedy Pro users. Generate your API key in Account Settings to begin connecting your AI assistants to your meeting intelligence.