jamie-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JAMIE_API_KEY | Yes | Your Jamie API key. Required. Must be generated from Settings → Developers → API Keys. | |
| JAMIE_KEY_TYPE | No | Determines which API routes are used. Options: 'personal' or 'workspace'. Defaults to 'personal'. | personal |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_meetingsA | List meetings from Jamie AI. Returns meeting IDs, titles, and timestamps. Use get_meeting to retrieve full details of a specific meeting. |
| get_meetingA | Get full details of a specific meeting: summary (markdown/html), transcript, participants, tasks, tags, and calendar event info. |
| 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. |
| 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. |
| list_tasksA | List action items and tasks extracted from meetings. |
| list_tagsA | List all available tags with their names and colors. Only available with a personal API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.