Skip to main content
Glama

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

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)

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.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

Available Tools

6 tools
delete_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

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    Six tools is a well-scoped set for a meeting intelligence server. Each tool covers a meaningful operation without unnecessary bloat or redundancy.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers