jamie-mcp
# jamie-mcp
MCP (Model Context Protocol) server for [Jamie AI](https://www.meetjamie.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` | List meetings with optional filters (date range, email, tag, pagination) |
| `get_meeting` | Get full meeting details: summary, transcript, participants, tasks, tags, calendar event |
| `delete_meeting` | Permanently delete a meeting and all its data (irreversible) |
| `search_meetings` | Semantic search across meeting content (personal key only) |
| `list_tasks` | List action items extracted from meetings |
| `list_tags` | List available tags with colors (personal key only) |
## Installation
Add this MCP server to your Claude configuration:
```json
{
"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.json` or project-level `.mcp.json`
## Configuration
### `JAMIE_API_KEY` (required)
Your Jamie API key. To generate one:
1. Open Jamie and go to **Settings → Developers → API Keys**
2. Click **Add API Key**
3. Choose a scope (Personal or Workspace) and give it a name
4. 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 |
|---|---|---|
| `"personal"` | `/v1/me/...` | Your own meetings + meetings shared with you |
| `"workspace"` | `/v1/workspace/...` | All meetings in the workspace |
> **Note:** `search_meetings` and `list_tags` are only available with a personal key.
## Requirements
- Node.js >= 18
- A Jamie AI account with Pro, Team, or Enterprise plan
## License
MIT
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.