Yes, Pocket AI works with Claude through Pocket’s official MCP server at https://public.heypocketai.com/mcp . Add it in Claude as a custom connector, sign in with your Pocket account, and Claude can search your recordings and read and update your action items. This is the Claude app path, on top of the Pocket AI recorder I use every day .
Try the recorder I use: Get Pocket . I use and pay for this.
Does Pocket AI work with Claude?
Two separate things get mixed up in that question.
The MCP connector is the one this page covers. You add Pocket’s remote MCP server in Claude, sign in, and Claude can search your recordings and read and update your action items.
Separately, Pocket’s own site says its summaries are “powered by GPT-5, Claude, and more.” That is Pocket picking models for the summary it writes in the app. Pocket does not document a control for you to pick Claude as the summary model, so I am not claiming you can.
What you need
A Pocket account. Search, action items, folders, and account info work on every plan. Full transcripts and questions that cut across meetings need Pocket Pro. If you just unboxed the device, set up the recorder first so you have something in the account to ask about.
A Claude plan that can add custom connectors: Free, Pro, Max, Team, or Enterprise. Custom connectors using remote MCP are available on Claude, Cowork, and Claude Desktop on those plans. Free allows one custom connector. Paid plans allow more. Claude on a free plan gets exactly one custom connector, so for a lot of people Pocket would be the only one.
Connect Pocket in Claude (web and desktop)
In Claude, open Customize, then Connectors, then Add, then Add custom connector. Name it (that name is what you see in the connectors list), paste https://public.heypocketai.com/mcp, and continue. Claude detects authentication settings from the server. Keep OAuth, the sign-in Pocket’s docs recommend, and finish by adding the connector. Sign in to Pocket when the browser prompt appears.
After it is added, enable it per chat from the plus button on the lower left of the chat, then Connectors. You will see your configured connectors with toggles so you can turn Pocket on for this conversation and leave it off for the next one.
Claude connects to that URL from Anthropic’s cloud, not from your laptop. That is true in the web app, in Claude Desktop, in Cowork, and on the mobile apps. Pocket’s server has to be reachable on the public internet from Anthropic’s IP ranges. A server on a private network will not connect even if you can reach it from your own machine.
On a Team or Enterprise plan
On Team, only Owners and Primary Owners can add a custom connector. On Enterprise, Owners, Primary Owners, and people with a custom role that includes Manage access to Libraries can add one. An owner adds it under Organization settings, then Connectors, then Add, then Custom, then Web. They give it a name and the Pocket URL, review the authentication settings, and add it to the organization.
Members then connect it themselves from Customize, then Connectors, and click Connect. Each person reaches only their own Pocket data, because each person signs in with OAuth. Pocket’s docs do not describe a shared API key for this Claude path, and a shared credential is the case Claude’s help center warns about: everyone who uses it would then see that credential’s access.
Connect Pocket in Claude Code
The command I use from the hub is:
claude mcp add --transport http pocket https://public.heypocketai.com/mcp
The first tool call opens a browser for Pocket sign-in. After that, Claude Code can search recordings and action items the same way the Claude app can.
API keys, config files, and the rest of the clients are a separate page. This one stays on the Claude app path.
Five prompts to try first
These are the ones I actually run, plus the ones Pocket’s docs suggest first:
- Show me my open Pocket action items from this week, grouped by who owns them.
- Pull context before a follow-up call: search the account’s folder, fetch the last transcript, and tell me what was promised and by whom.
- What did I discuss last week?
- Mark that follow-up action as done.
- Find ideas across recordings, the half-formed ones I talked through on a walk.
The first one is the daily drain. Status changes sync back to the Pocket app, so closing an item from Claude is the same as closing it there. Pocket’s docs also list prompts like listing this week’s recordings, fetching the last transcript, searching for a tag, and bumping the priority of open reminders. Those are Pro-gated where they need a full transcript. The five above are the ones I actually start with.
What Claude can and can’t do with your Pocket data
| What | Plan |
|---|---|
| Search conversations | Every plan |
| Search and update action items | Every plan |
| List folders and spaces | Every plan |
| Account info | Every plan |
| Full transcript with summary | Pro |
| Questions across meetings | Pro |
Updates you make to an action item sync back to the Pocket app. Pocket documents status, priority, due date, label, context, and assignee as the fields you can change, and setting COMPLETED stamps the time. Search without a query returns recent transcripts, newest first and paged. Search with a query returns up to 8 section hits. Pro’s transcript tool also returns a signed audio URL that lasts an hour, so a link you paste into notes is dead by the next meeting.
It acts as you
The connector reaches everything your Pocket account can see. Folder scoping is a filter Claude applies when it searches, not a permission the server enforces. It authenticates the person, not the agent
. If the recording is in your account, Claude can find it. Treat write tools, including update_pocket_actionitem, as something you approve before they run if you do not want Claude editing the list unsupervised.
The connection comes from Anthropic’s cloud
Claude connects to Pocket from Anthropic’s servers, not your laptop. A laptop firewall that blocks the Pocket URL will not stop the connector. The Pocket server has to be reachable on the public internet from Anthropic’s IP ranges. Local MCP servers in Claude Desktop’s config file are a separate mechanism and do use your local network, but they are not this connector.
How to disconnect Pocket from Claude
Open Customize, then Connectors. Click Remove, or open the three dots next to Pocket and follow the prompts. That drops the connector on the Claude side. Team and Enterprise owners can remove it for the organization under Organization settings, then Connectors. If you need to change the URL or the name, Claude’s help center says you remove it first and add it again.
If you used an API key anywhere, regenerate it in Pocket settings. An API key is a long-lived secret for the whole account, which is why I keep long-lived keys out of the agent when I can use OAuth instead.