Pocket MCP Server Setup for Claude, Cursor, and AI Tools

Connect Pocket recordings to Claude, Cursor, Littlebird, and other MCP-compatible AI tools

We’re excited to announce Pocket MCP Server – a new way to connect your Pocket recordings directly to AI assistants like Claude, Cursor, Littlebird, and other MCP-compatible tools.

What is MCP?

Model Context Protocol (MCP) is an open standard that lets AI assistants securely access your data. With Pocket’s MCP server, you can now ask AI questions about your recordings, search across all your transcripts, and get insights – all within your favorite AI tools.

What can you do with it?

"What did I discuss in my meetings last week?"
"Find all recordings where I talked about the product launch"
"Summarize my conversation from yesterday"
Search across all your recordings without leaving your workflow

Setup Instructions

Pocket MCP supports both OAuth (recommended) and API keys. OAuth is the simplest option for most clients; API keys are available for clients that only support static headers.

Option 1: OAuth (recommended)

OAuth is the fastest path. Add Pocket as a remote MCP server and follow the OAuth login prompt to authorize access.

MCP server URL

https://public.heypocketai.com/mcp

Option 2: API key (manual headers)

Get your API key from Pocket Settings → Developer → API Keys. Your key starts with pk_....

Pocket MCP accepts either header format:

Authorization: Bearer pk_... (recommended), or
Authorization: ApiKey pk_...

If your client uses mcp-remote, make sure the Authorization header is forwarded with the --header argument.

Note: Some MCP clients (including Claude Desktop and Cursor) can mangle command arguments that contain spaces. The examples below use Authorization:${AUTH_HEADER} with a separate AUTH_HEADER environment variable to avoid this issue.

Cursor

OAuth install (recommended):

Manual setup with API key:

Open Cursor Settings (Cmd/Ctrl + ,)
Search for "MCP" or go to Features → MCP Servers
Click Add Server and enter:

{
  "pocket": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://public.heypocketai.com/mcp",
      "--header",
      "Authorization:${AUTH_HEADER}"
    ],
    "env": {
      "AUTH_HEADER": "Bearer pk_your_api_key_here"
    }
  }
}

Restart Cursor.

Claude Desktop

OAuth (recommended):

Open Claude Desktop → Settings → Connectors
Click Add custom connector
Paste the MCP server URL: https://public.heypocketai.com/mcp
Click Connect and finish the OAuth flow

API key (manual config):

Open config file:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this configuration:

{
  "mcpServers": {
    "pocket": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://public.heypocketai.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer pk_your_api_key_here"
      }
    }
  }
}

Restart Claude Desktop.
Look for the 🔌 icon showing Pocket tools are connected.

Claude Code (CLI)

Run this command to add Pocket MCP:

claude mcp add pocket --transport http https://public.heypocketai.com/mcp --header "Authorization: Bearer pk_your_api_key_here"

Or add manually to ~/.claude/settings.json:

{
  "mcpServers": {
    "pocket": {
      "type": "http",
      "url": "https://public.heypocketai.com/mcp",
      "headers": {
        "Authorization": "Bearer pk_your_api_key_here"
      }
    }
  }
}

Restart Claude Code after adding.

Littlebird

Pocket is available as an official Littlebird integration.

Open Littlebird Settings
Go to Integrations
Click Add integration
Search for Pocket and follow the prompts to connect your account

Windsurf

Add to your Windsurf MCP config (~/.windsurf/mcp.json):

{
  "mcpServers": {
    "pocket": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://public.heypocketai.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer pk_your_api_key_here"
      }
    }
  }
}

Cline (VS Code Extension)

Open VS Code Settings
Search for "Cline MCP"
Add to MCP Servers configuration:

{
  "pocket": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://public.heypocketai.com/mcp",
      "--header",
      "Authorization:${AUTH_HEADER}"
    ],
    "env": {
      "AUTH_HEADER": "Bearer pk_your_api_key_here"
    }
  }
}

Generic MCP Client (Direct HTTP)

For any MCP-compatible client that supports HTTP transport:

Endpoint: https://public.heypocketai.com/mcp
Transport: Streamable HTTP
Auth Header: Authorization: Bearer pk_your_api_key_here
Required Headers:
- Content-Type: application/json
- Accept: application/json, text/event-stream

Available Tools

Some tools are available on Pro plans only, mirroring the gating used by other remote MCP servers. Basic search and account info stay available to all plans; transcripts, folders, folder filtering, and the natural-language query tool are Pro-only.

Tool	Plan	Description
`search_pocket_conversations`	All plans	Search conversations. With a `query` it returns the most relevant section hits; without a `query` it returns recent full transcripts with pagination. Folder filtering (`folderIds`) is Pro-only
`search_pocket_actionitems`	All plans	Search action items with status/priority/category/due date filters
`get_account_info`	All plans	Return the authenticated user's email, display name, plan (free or pro), and active organization
`get_pocket_conversation`	Pro only	Fetch full transcripts for specific recordings, including the AI-generated summary (Notes) and signed audio URLs
`list_pocket_folders`	Pro only	List the user's folders and spaces with recording counts
`query_pocket_meetings`	Pro only	Ask a natural-language question about your meetings; returns a synthesized answer plus the source recording ids

Tool Details

get_pocket_conversation (Pro only)

recording_ids (array) — Recording IDs to fetch transcripts for
Response includes:
- recordingId, recordingTitle, recordingDate, recordingTags, audioUrl
- transcriptSegments: array of transcript segments in seconds with shape { text: string, start: number, end: number, speaker?: string }
- summary: the AI-generated summary shown in the Notes tab (from the most recent summarization), omitted if no summary exists yet
- transcript (plain flattened text) is no longer returned

Example segment-based response:

{
  "success": true,
  "data": [
    {
      "recordingId": "rec_123",
      "recordingTitle": "Weekly Sync",
      "recordingDate": "2026-03-25T15:04:05Z",
      "recordingTags": ["meeting", "product"],
      "transcriptSegments": [
        { "text": "Let's review the launch plan.", "start": 0.62, "end": 4.88, "speaker": "Alex" },
        { "text": "We should finalize QA by Friday.", "start": 5.21, "end": 9.77, "speaker": "Unknown Speaker 2" }
      ],
      "summary": { "...": "AI-generated summary content (Notes tab)" },
      "audioUrl": {
        "signedUrl": "https://...",
        "expiresIn": 3600,
        "expiresAt": "2026-03-25T16:04:05Z"
      }
    }
  ]
}

search_pocket_conversations

This tool operates in two modes depending on whether query is provided.

query (string, optional) — Semantic + keyword search query. When provided, the tool runs query mode; when omitted, it runs recency mode.
recordingDateAfter (string) — Filter recordings after this date (ISO 8601)
recordingDateBefore (string) — Filter recordings before this date (ISO 8601)
tags (array) — Filter by tag names
folderIds (array) — Filter to recordings in these folder or space ids. Pro only; ignored for non-pro callers.

Query mode (query provided): hybrid vector + BM25 section search. Returns up to 8 of the most relevant section-level hits with timestamps and summaries.

Recency mode (query omitted): returns the most recent full transcripts within the optional date range, sorted newest-first, with pagination metadata. Recording objects include:

transcriptSegments: array of transcript segments with shape { text: string, start: number, end: number, speaker?: string }
transcript: flattened speaker-prefixed text retained for compatibility

Recency mode also accepts recordingDateBeforeExclusive for paging. If data.meta.hasMore is true, call again with the same filters and set recordingDateBeforeExclusive = data.meta.nextRecordingDateBeforeExclusive to fetch the next older page.

list_pocket_folders (Pro only)

No parameters
Response includes the user's spaces and child folders, each with id, name, kind (space or folder), parent folder id, and recording counts (recordingCount / totalRecordingCount)

query_pocket_meetings (Pro only)

query (string, required) — Natural-language question about your meetings and recordings
language (string, optional) — Response language, e.g. "English (US)"
Response includes:
- answer: the synthesized natural-language answer
- sourceRecordings: the recordings the assistant used to answer

get_account_info

No parameters
Response includes userId, email, displayName, plan (e.g. free or pro), tier (free or pro), and organization (when the user belongs to one)

search_pocket_actionitems

query (string) — Search term within action item title/description
status (string) — TODO, IN_PROGRESS, COMPLETED, CANCELLED
priority (string) — CRITICAL, HIGH, MEDIUM, LOW
category (string) — TASK, MEETING, REMINDER
dueBefore (string) — Filter items due before date (ISO 8601)
dueAfter (string) — Filter items due after date (ISO 8601)
recordingDateFrom (string) — Filter source recordings after this date (ISO 8601)
recordingDateTo (string) — Filter source recordings before this date (ISO 8601)

Example Prompts

Once connected, try asking:

"List my recordings from this week"
"Get the transcript from my last recording"
"What tags do I have in Pocket?"
"Find recordings tagged with ‘meeting’"
"Search for discussions about budget planning"
"What did I talk about regarding the product launch?"
"Find action items related to the Q1 roadmap"

Troubleshooting

Tools not showing up?

Make sure you restarted the app after adding config
Check that your API key is correct (starts with pk_)
Verify the config file JSON is valid

Authentication errors?

Regenerate your API key in Pocket Settings
Check that your key starts with pk_
If using mcp-remote, confirm you are forwarding the Authorization header with --header
Make sure there are no extra spaces or newlines in the key value

Pocket MCP Server