> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetjamie.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP

> Connect Claude, ChatGPT, Cursor, and other AI tools to your Jamie meeting notes

Connect your AI tools to your Jamie meeting notes with MCP (Model Context Protocol). Once connected, you can search through your meetings, find specific topics discussed in past meetings, extract action items, and answer questions based on your meeting history — all from your favorite AI assistant.

<Note>
  MCP is available on the **Pro**, **Team**, and **Enterprise** plans. If you're
  on the Free or Plus plan, [upgrade your
  plan](https://www.meetjamie.ai/pricing) to connect your AI tools.
</Note>

<Info>
  We're working on adding Jamie to the Claude and ChatGPT connector directories
  for one-click setup. In the meantime, you can connect by adding Jamie as a
  custom MCP server using the instructions below.
</Info>

## Pre-requisites

* A Jamie account on a Pro, Team, or Enterprise plan, with existing meeting notes
* An AI tool that supports MCP, such as Claude, ChatGPT, Cursor, Windsurf, or Microsoft Copilot

## How to connect

### Claude

<Note>
  Custom connectors require a Claude Pro, Max, Team, or Enterprise plan. Free
  users are limited to one custom connector.
</Note>

1. Open [Claude](https://claude.ai) and sign in
2. Go to [**Customize → Connectors**](https://claude.ai/customize/connectors)
3. Click **+** then **Add custom connector**
4. Enter the Jamie MCP server URL:

```text theme={null}
https://mcp.meetjamie.ai/mcp
```

5. Click **Add**, then complete the OAuth sign-in with your Jamie account
6. In a new chat, click **+** → **Connectors** and toggle Jamie on

<Tip>
  On Team and Enterprise plans, an Owner must first add the connector in
  [**Organization settings →
  Connectors**](https://claude.ai/admin-settings/connectors). Members can then
  connect to it from **Customize → Connectors**.
</Tip>

### ChatGPT

<Note>MCP connectors require a ChatGPT Plus, Pro, or Enterprise plan.</Note>

1. Open [ChatGPT](https://chatgpt.com) and sign in
2. Go to **Settings → Connectors** (or **Developer** section)
3. Enable **Developer Mode** if not already enabled
4. Add a new connector with the URL:

```text theme={null}
https://mcp.meetjamie.ai/mcp
```

5. Set authentication type to **OAuth** and complete the sign-in flow
6. In a new chat, click **+** → **More → Developer mode** and toggle Jamie on

### Microsoft Copilot

Jamie is available as a connector in **Microsoft Copilot Studio**, where you build and extend the agents used by Microsoft 365 Copilot. You add Jamie as a Model Context Protocol tool on an agent, and that agent can then read your meetings, transcripts, tasks, and tags.

<Note>
  Connecting an MCP server requires a Copilot Studio license, and the agent must
  have **generative orchestration** turned on (in the agent's **Settings**). MCP
  tools don't work with classic orchestration.
</Note>

1. In [Copilot Studio](https://copilotstudio.microsoft.com), open the agent you want to extend
2. Go to the **Tools** page for your agent
3. Select **Add a tool**
4. Select **Model Context Protocol** — a list of available MCP connectors appears
5. Find and select **Jamie AI**
6. Authorize the connection — sign in with your Jamie account when prompted
7. Select **Add and configure**

Jamie's tools are added and turned on by default. To limit which ones the agent can use, open the Jamie tool from the **Tools** tab, turn off **Allow all**, and use the individual toggles.

### Claude Code

1. Run `claude` in your terminal
2. Add the Jamie MCP server:

```bash theme={null}
claude mcp add jamie --transport http https://mcp.meetjamie.ai/mcp
```

3. Open a new terminal tab and run `claude` again
4. Run `/mcp`, select the Jamie MCP, and select **Authenticate**
5. Ask Claude to reference your meetings

### Cursor

1. Open **Cursor Settings** (Cmd+Shift+J) → **Tools & MCP**
2. Click **Add new MCP server**
3. Set the type to **Streamable HTTP** and enter the URL:

```text theme={null}
https://mcp.meetjamie.ai/mcp
```

4. Click **Install** — a browser window will open for OAuth authentication
5. Sign in with your Jamie account
6. Your meeting tools will appear in the MCP panel

You can also add it via `.cursor/mcp.json` in your project or `~/.cursor/mcp.json` globally:

```json theme={null}
{
  "mcpServers": {
    "jamie": {
      "url": "https://mcp.meetjamie.ai/mcp"
    }
  }
}
```

### Windsurf

1. Open **Windsurf Settings → MCP**
2. Add a new server with the URL:

```text theme={null}
https://mcp.meetjamie.ai/mcp
```

3. Complete OAuth authentication when prompted

### Other AI tools

You can connect any MCP-compatible tool using the public URL:

```text theme={null}
https://mcp.meetjamie.ai/mcp
```

Your AI tool must support:

* [Streamable HTTP transport](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http)
* **OAuth 2.0 authentication** — Jamie uses browser-based OAuth, so your tool needs to open a browser window for you to sign in. No API keys or client secrets are needed — credentials are handled automatically via Dynamic Client Registration.

## Available tools

Once connected, these tools are available to your AI assistant:

| Tool                       | Description                                                                                                          | Example prompts                                                           |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| `list_meetings`            | List your meetings with optional date range, tag filter, and pagination                                              | *What meetings did I have last week?*                                     |
| `get_meeting`              | Get full details of a meeting including summary, transcript, tasks, and participants                                 | *Show me the notes from my standup this morning*                          |
| `get_meeting_transcript`   | Read a long meeting's full transcript in sequential pages (use after `get_meeting` when its transcript is truncated) | *Get the complete transcript of yesterday's planning call*                |
| `search_meetings`          | Semantic search across your meeting content (last 6 months by default)                                               | *What did the team decide about the pricing change?*                      |
| `search_people`            | Look up people from your contacts by email address, with their name, role, and company when available                | *Who is [jordan@acme.com](mailto:jordan@acme.com) and what's their role?* |
| `list_tasks`               | List action items from your meetings with filters for date, status, and assignee                                     | *What are my open action items?*                                          |
| `list_tags`                | List all tags available to you, including tags shared by teammates                                                   | *What tags do I have?*                                                    |
| `create_tag`               | Create a new tag (label) you own, with an optional color                                                             | *Create a tag called "Q3 Planning"*                                       |
| `update_tag`               | Rename a tag you own and/or change its color                                                                         | *Rename my "Sales" tag to "Revenue"*                                      |
| `delete_tag`               | Permanently delete a tag you own (removes it from all meetings; cannot be undone)                                    | *Delete the "Old Project" tag*                                            |
| `set_tag_sharing`          | Share a tag you own with workspace teammates, or make it private                                                     | *Share my "Hiring" tag with [sam@acme.com](mailto:sam@acme.com)*          |
| `add_tag_to_meetings`      | Add a tag to one or more meetings you own                                                                            | *Tag yesterday's interview with "Hiring"*                                 |
| `remove_tag_from_meetings` | Remove a tag from one or more meetings you own                                                                       | *Remove the "Hiring" tag from that meeting*                               |

## Troubleshooting

### MCP tools not working

If your AI tool can't access your meeting notes, try re-authenticating by disconnecting and reconnecting.

### "No tools available" in Claude

If Jamie is connected but shows **No tools available**:

1. Go to [Customize → Connectors](https://claude.ai/customize/connectors) (must be on claude.ai, even if you use the desktop app)
2. Find the Jamie connector
3. Click the three-dot menu and choose **Remove**
4. Re-add the connector using the URL `https://mcp.meetjamie.ai/mcp` and complete authentication

### Authentication errors

Make sure you're signing in with the same email address your Jamie account is registered under. You can verify your account email in the Jamie app under **Settings → Account**.

## FAQ

<AccordionGroup>
  <Accordion title="Do I need the same email for my AI tool and Jamie?">
    No. You can use different accounts. During the OAuth flow, you'll authenticate the Jamie account you want to give access to.
  </Accordion>

  <Accordion title="Do I need a client ID or client secret?">
    No. Jamie MCP uses Dynamic Client Registration (DCR), so credentials are
    created automatically. If a third-party platform shows client ID/secret
    fields, leave them blank.
  </Accordion>

  <Accordion title="Can I connect Jamie MCP to my own internal AI tool?">
    Yes — any tool implementing the [MCP client specification](https://modelcontextprotocol.io/) with Streamable HTTP transport can connect. Your tool needs to handle the OAuth 2.0 browser authentication flow. See the "Other AI tools" section above for details.
  </Accordion>
</AccordionGroup>
