migas-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@migas-mcp search transcripts for roadmap discussion"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
migas-mcp
MCP server for Migas meeting transcripts. Query your local meeting data from Claude Desktop, Claude Code, Cursor, or any MCP-compatible AI assistant.
What it does
Migas transcribes your meetings locally on your Mac. This MCP server gives AI assistants read-only access to that data so you can ask questions like:
"What did we discuss about the roadmap last week?"
"What has Sarah said about the budget across all meetings?"
"Show me the transcript from yesterday's standup"
Related MCP server: transcripts
Tools
Tool | Description |
| Recent meetings with title, date, duration, participants |
| Full speaker-labeled transcript for a meeting |
| Full-text search across all meeting transcripts |
| Look up enrolled speakers by name |
| Everything a speaker said across all meetings |
Install
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"migas": {
"command": "npx",
"args": ["-y", "migas-mcp"]
}
}
}Claude Code
claude mcp add migas -- npx -y migas-mcpCursor
Add to MCP settings:
{
"mcpServers": {
"migas": {
"command": "npx",
"args": ["-y", "migas-mcp"]
}
}
}Requirements
Migas installed and launched at least once (creates the local database)
macOS (reads from
~/Library/Application Support/Migas/meetings.db)
Privacy
The MCP server is read-only and connects to your local Migas database. No meeting data is sent anywhere by the server itself. When you ask an AI assistant a question, only the relevant transcript text is sent to the AI provider, same as using Migas's built-in chat.
Development
bun install
bun test
bun run buildAvailable Tools
5 toolsfind_speakersA
Look up enrolled speakers by name. Returns candidates with IDs for use with get_speaker_contributions. Only returns speakers with stable cross-meeting identities (not transient per-meeting guests).
Inputs: name (required).
get_meeting_transcriptA
Get the full transcript for a specific meeting with speaker labels and timestamps.
Inputs: meeting_id (required).
get_speaker_contributionsA
Get everything a specific enrolled speaker said across all meetings. Use find_speakers first to get the speaker ID.
Inputs: speaker_id (required).
list_meetingsA
List recent meetings with title, date, duration, and participant names.
Inputs: limit, since_date.
search_transcriptsA
Search across all meeting transcripts using full-text search. Returns matching segments with meeting context and speaker attribution.
Inputs: query (required), limit, meeting_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing meetings, retrieving a transcript, searching transcripts, finding speakers, and aggregating speaker contributions. There is no functional overlap or ambiguity between tools.
All tool names follow the same verb_noun pattern in snake_case (e.g., list_meetings, get_meeting_transcript, search_transcripts), which makes the naming scheme predictable and consistent across the entire set.
Five tools is a well-scoped count for a meeting transcription and speaker analytics server. Each tool covers a distinct functional area without redundancy or excessive granularity.
The server provides complete coverage of its core domain: browsing meetings, reading transcripts, full-text search, and per-speaker contribution analysis. There are no obvious gaps or dead ends in the workflow.
Maintenance
Related MCP Connectors
Read-only access to your AIMochi meeting notes: list, search and read transcripts and summaries.
Meeting transcripts for AI agents: search calls, read who said what, transcribe files and links.
Read your SummitScribe meeting notes, transcripts and action items. Read-only.
Read your epoc meeting transcripts: list synced meetings and read their transcripts. Read-only.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceProvides read-only access to Google Drive meeting transcripts and Google Calendar events, enabling AI assistants to search, analyze, and retrieve meeting insights.2-
- FlicenseNot gradedqualityCmaintenanceEnables an AI agent to list, read, and search local meeting transcript files, returning structured transcript information and search hits. The server enforces read-only access confined to a transcripts directory with .txt and .md files only.-
- AlicenseAqualityCmaintenanceExposes meeting transcripts to any MCP-capable AI client so it can list meetings, page through a single transcript, and search across all of them for a topic with exact timestamps. Speaker labels, emails, phone numbers, and paths are pseudonymized or redacted before anything crosses the protocol, and transcripts are read-only.3MIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to what you have dictated and what was said in your recorded meetings, so coding agents like Codex, Claude Code, Pi or LM Studio can search your local transcripts and notes.MIT