Mcp Server
Pull Convo meeting transcripts, summaries, and action items into Claude or Cursor so shipping work stays aligned with what was actually decided.
Overview
Convo MCP is a Build-phase MCP server that lets AI assistants access your Convo meetings, transcripts, summaries, and action items.
What is this MCP server?
- stdio MCP via @itsconvo/mcp-server npm package version 1.0.3
- Read Convo meetings, transcripts, summaries, and action items from the agent
- Single required secret CONVO_API_KEY (convo_ prefix) from Convo app Settings
- Purpose-built for any MCP assistant, not a single-editor skill file
- One required environment variable: CONVO_API_KEY
- stdio transport via @itsconvo/mcp-server on npm
Community signal: 1 GitHub stars.
What problem does it solve?
Your decisions live in Convo recordings while your agent only sees the repo, so you retype meeting outcomes into every planning session.
Who is it for?
Solo founders who record calls in Convo and want Cursor or Claude Code to reference transcripts and summaries while building.
Skip if: Teams not using Convo, or workflows that need live meeting bots without an API key from the Convo app.
What do I get? / Deliverables
Once CONVO_API_KEY is set, your agent can retrieve Convo meeting content and action items to inform specs, tasks, and replies in chat.
- Agent-readable Convo meetings, transcripts, summaries, and action items over MCP
- Local stdio MCP server wired with a single API key
Recommended MCP Servers
Journey fit
Meeting artifacts feed specs and task lists during Build, where solo builders turn calls into concrete PM inputs. PM is where transcripts, summaries, and action items become backlog context and follow-ups without rewatching recordings.
How it compares
Convo account MCP bridge, not an in-repo meeting-notes skill or generic calendar integration.
Common Questions / FAQ
Who is io.github.itsconvo/mcp-server for?
It is for Convo users who want MCP-enabled agents to read their meetings, transcripts, summaries, and action items during development and planning.
When should I use io.github.itsconvo/mcp-server?
Use it when you regularly ship from Convo-recorded discussions and need the agent to pull exact wording, summaries, or action items into PM work.
How do I add io.github.itsconvo/mcp-server to my agent?
Install @itsconvo/mcp-server, create a CONVO_API_KEY in Convo Settings, and add the stdio server plus that env var to your MCP client configuration.