Pocket MCP Server

We’re excited to announce Pocket MCP Server – a new way to connect your Pocket recordings directly to AI assistants like Claude, Cursor, 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:

1. Open Cursor Settings (Cmd/Ctrl + ,)
2. Search for "MCP" or go to Features → MCP Servers
3. 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"
    }
  }
}

4. Restart Cursor.

Claude Desktop

OAuth (recommended):

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

API key (manual config):

1. Open config file:
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
2. 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"
      }
    }
  }
}

3. Restart Claude Desktop.
4. 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.

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)

1. Open VS Code Settings
2. Search for "Cline MCP"
3. 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

Tool Details

get_pocket_conversation

• recording_ids (array) — Recording IDs to fetch transcripts for

search_pocket_conversations

• query (string) — Semantic + keyword search query
• recordingDateAfter (string) — Filter recordings after this date (ISO 8601)
• recordingDateBefore (string) — Filter recordings before this date (ISO 8601)
• tags (array) — Filter by tag names

search_pocket_conversations_timerange

• recordingDateAfter (string) — Filter recordings after this date (ISO 8601)
• recordingDateBefore (string) — Filter recordings before this date (ISO 8601)
• tags (array) — Filter by tag names

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

This is our first release – feedback welcome! Let us know what’s working and what needs improvement.