jamie-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., "@jamie-mcp list my meetings from yesterday"
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.
jamie-mcp
MCP (Model Context Protocol) server for Jamie AI — the AI meeting assistant. This server allows Claude to interact with your Jamie account: list meetings, read summaries and transcripts, search across meetings, manage tasks, and more.
Tools
Tool | Description |
| List meetings with optional filters (date range, email, tag, pagination) |
| Get full meeting details: summary, transcript, participants, tasks, tags, calendar event |
| Permanently delete a meeting and all its data (irreversible) |
| Semantic search across meeting content (personal key only) |
| List action items extracted from meetings |
| List available tags with colors (personal key only) |
Related MCP server: MCP Fathom Server
Installation
Add this MCP server to your Claude configuration:
{
"mcpServers": {
"jamie": {
"command": "npx",
"args": ["-y", "github:vicampuzano/jamie-mcp"],
"env": {
"JAMIE_API_KEY": "jk_your_api_key_here",
"JAMIE_KEY_TYPE": "personal"
}
}
}
}Where to add this configuration
Claude Desktop:
~/Library/Application Support/Claude/claude_desktop_config.json(macOS) or%APPDATA%\Claude\claude_desktop_config.json(Windows)Claude Code:
~/.claude.jsonor project-level.mcp.json
Configuration
JAMIE_API_KEY (required)
Your Jamie API key. To generate one:
Open Jamie and go to Settings → Developers → API Keys
Click Add API Key
Choose a scope (Personal or Workspace) and give it a name
Copy the key immediately — it is only shown once
All keys start with the jk_ prefix. API access requires a Pro, Team, or Enterprise plan.
JAMIE_KEY_TYPE (optional)
Determines which API routes are used. Defaults to "personal".
Value | Routes | Access scope |
|
| Your own meetings + meetings shared with you |
|
| All meetings in the workspace |
Note:
search_meetingsandlist_tagsare only available with a personal key.
Requirements
Node.js >= 18
A Jamie AI account with Pro, Team, or Enterprise plan
License
MIT
Available Tools
6 toolsdelete_meetingA
PERMANENTLY delete a meeting and ALL its data (summary, transcript, tasks). This action is IRREVERSIBLE. Always confirm with the user before calling this tool.
Inputs: meetingId (required).
get_meetingA
Get full details of a specific meeting: summary (markdown/html), transcript, participants, tasks, tags, and calendar event info.
Inputs: meetingId (required).
list_meetingsA
List meetings from Jamie AI. Returns meeting IDs, titles, and timestamps. Use get_meeting to retrieve full details of a specific meeting.
Inputs: tag, limit, cursor, endDate, +2 more.
list_tagsA
List all available tags with their names and colors. Only available with a personal API key.
Inputs: no named parameters.
list_tasksA
List action items and tasks extracted from meetings.
Inputs: limit, cursor.
search_meetingsA
Semantic search across meeting content. Returns matching text excerpts with meeting references. Max 40 results from the past 6 months. Only available with a personal API key.
Inputs: query (required), endDate, startDate.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct action and resource: listing, fetching, searching, deleting meetings, plus listing tags and tasks. The only mild overlap is tasks appearing in get_meeting, but list_tasks clearly serves as the cross-meeting task index.
All tools follow a consistent verb_noun snake_case pattern: list_, get_, delete_, search_. The verbs are simple and predictable, making the tool surface easy to navigate.
Six tools is a well-scoped set for a meeting intelligence server. Each tool covers a meaningful operation without unnecessary bloat or redundancy.
The core meeting lifecycle is covered: discover, retrieve, search, and delete, along with tag and task listing. Update and task-management operations are absent, but are likely unnecessary given Jamie's automatic meeting ingestion and read-focused purpose.
Maintenance
Related MCP Connectors
Connect Claude to Fathom meeting recordings, transcripts, and summaries
Ask Claude about your meetings: summaries, action items and transcripts from Roomtone
Start meetings and work with meeting transcripts, notes, recordings and follow-up tasks.
Lets Claude, ChatGPT, and Muse read and update your beckett tasks, notes, calendar, and lists.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceExposes the Fathom AI meeting intelligence API to Claude, allowing users to list meetings, fetch transcripts, and retrieve summaries. It also enables management of teams and members through the Model Context Protocol.46 npmMIT
- AlicenseAqualityDmaintenanceEnables Claude to search and retrieve meeting information from Fathom AI through natural language queries.28MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to access your Fathom meetings, transcripts, and AI summaries.16 npm16MIT
- AlicenseAqualityCmaintenanceEnables Claude Desktop and MCP clients to access Fathom meeting intelligence, including listing meetings, retrieving summaries and transcripts, and searching by title.441 npmMIT