🚀 Pocket MCP Server

[mhirrrr]

Hey everyone,

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

Prerequisites

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

---

Claude Desktop

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.

---

Cursor

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

Cursor One Click Install

---

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	Description
pocket_list_recordings	List and filter recordings by date, tags
pocket_get_recording	Get full transcript and summary
pocket_get_recording_audio_url	Get temporary audio download link
pocket_list_tags	Browse all your tags

---

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’”

---

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
• Make sure there are no extra spaces in the key

---

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

Get your API key: Pocket Settings → Developer → API Keys

[atun_grande]

I’ve been trying to get this to work through Claude Desktop, but I keep getting authentication errors, even after regenerating the API key, doublechecking for extra spaces, and restarting Claude Desktop. After some back and forth, this is what Claude suggested:

Contact Pocket support: If the above doesn’t work, this appears to be an issue with their mcp-remote wrapper not properly handling authentication. Ask them:

• What env variable name their MCP server expects

• Whether there’s a known issue with Bearer token authentication

[mhirrrr]

hey @atun_grande can you please dm us the error you are facing

[mhirrrr]

we have edited the docs please do let us know how it goes now

[Stephenp]

I’m excited to try this out!

[atun_grande]

Adding the header info to the config fixed the error. Working great now!

[ansb29]

Hey @atun_grande , can you share what helped? I am getting authentication error with Claude desktop. Thanks

@mhirrrr I am using the json code with my api key added and replacing whatever was included in the Claude desktop config file. Lemme know if I am missing something. Thanks

[mhirrrr]

hey @ansb29 we updated the above configs did you use the updated one?

[ansb29]

Used what I see in this thread from a few minutes back.

[ansb29]

Here’s the config code @mhirrrr

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

[atun_grande]

I am no expert, but it looks like you might have some typos. Pasting this straight from my config file:

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

[ansb29]

Used your code with my api key. Still the same server disconnected error. @mhirrrr

[mhirrrr]

this seems to be a local node version problem we are figuring out and workaround

[ansb29]

Installed node.js on my Mac. Server is connected now.

[mhirrrr]

so we just checked this looks like a claude desktop issue we are getting in touch with our partners to get this figured out. meanwhile cursor has been working great

[RandallK]

I use ChatGPT, will this work with your new process?

[mhirrrr]

hey we will update docs.heypocketai.com with the oauth setup as well to use it with chatgpt will keep you updated

[JeremiahSvaren]

Just wanted to say, I’ve been using the MCP server with Claude and I’ve been super happy with it!

[JeremiahSvaren]

heads up that link is incorrect, this is the correct link: Welcome to Pocket

[arigsbee]

I have worked out a short guide to bridging Pocket AI to Open WebUI: A Proxy Guide for Local LLMs

The Challenge

Directly connecting the Pocket MCP Server to Open WebUI often results in “cannot pickle object” errors or persistent HTTP 403 Forbidden crashes on local hardware. These issues typically stem from serialization conflicts with the asynchronous MCP stream.

Phase 1: Building the Foundation (The MCPO Proxy)

The MCPO (MCP-to-OpenAPI) Proxy is the critical translator. It converts the complex MCP protocol into standard OpenAPI (REST) calls that local models handle much more reliably.

* Configure Outbound Auth (config.json):

Create a config.json file to store your Pocket AI credentials securely. This ensures the proxy handles the “Outbound” handshake secretly.

{

“mcpServers”: {

"pocket": {

  "type": "streamable-http",

  "url": "https://public.heypocketai.com/mcp",

  "headers": {

    "Authorization": "Bearer pk_your_pocket_key_here"

  }

}

}

}

(Note: Ensure there is exactly one space between ‘Bearer’ and your key to avoid 403 errors.)

* Deploy the Container (docker-compose.yml):

Use an “Inbound” secure key (MCPO_API_KEY) to protect the proxy from unauthorized local access.

 mcpo:

image: ghcr.io/open-webui/mcpo:main

container_name: mcpo

environment:

  - MCPO_API_KEY=your_secure_inbound_key

volumes:

  - ./mcpo:/app/config

command: 'mcpo --config /app/config/config.json --port 8000 --api-key your_secure_inbound_key'

Phase 2: Connecting the Interface (Open WebUI)

Once the proxy is running and verified via logs (API Key: Provided), link it to your interface.

* Tool Registration: Add the tool as an OpenAPI type (not MCP) using your proxy URL: http://mcpo:8000/pocket.

* Model Tool-Binding: Models do not “see” the proxy by default. You must navigate to Workspace > Models > Edit Model and toggle the Pocket tools ON.

* Advanced Parameters (Critical):

* Function Calling Mode: Change this from “Native” to Default for models like DeepSeek-R1. “Default” uses a prompt-based template that is far more stable for reasoning models communicating with proxies.

Phase 3: The Model Handshake (System Prompts)

Reasoning models like DeepSeek-R1 can sometimes “overthink” tool parameters, leading to empty results. A “Hardened” system prompt ensures the model executes the call correctly every time:

> “You have access to the ‘Hey Pocket AI’ tools. If the user asks for recordings or summaries, you MUST use the available tools to fetch the data before answering. Use the pocket_list_recordings tool with NO filters. Do not add any search terms. Just fetch the list of every recording you can see.”

>

Summary of Benefits

* Stability: Eliminates asyncio pickling crashes.

* Security: Segregates Inbound (Proxy Auth) and Outbound (Pocket API Auth).

* Compatibility: Enables DeepSeek-R1 to pull transcripts and

summaries seamlessly without reasoning loops.