# Pocket and Your AI Agent: Why I Connect Them > Why I connect Pocket to an AI agent: search meetings, pull action items, and ask questions across recordings. Setup lives on the Claude and MCP pages. - Canonical URL: https://webofmike.com/pocket-ai-agent/ - Author: Mike Moore (https://webofmike.com/about/) - Published: 2026-10-22 - Last modified: 2026-10-22 - Tags: AI Tools, Productivity, MCP - Cite as: Mike Moore, "Pocket and Your AI Agent: Why I Connect Them", Web of Mike (webofmike.com), 2026-10-22. https://webofmike.com/pocket-ai-agent/ Heads up: some links here are affiliate links. If you buy through them I may earn a commission, at no extra cost to you. It doesn't change what I recommend. The recorder is how I capture a meeting. The useful part is that an AI agent can search it later. I connect Pocket to the assistant that already runs my day. This page is why. It is not the install. For the Claude app path, use [connect Pocket AI to Claude](/connect-pocket-ai-to-claude/). For the URL, sign-in, other clients, and every tool, use the [Pocket MCP server](/pocket-mcp-server/) page. I am not repeating those steps here. ## What changes once it is connected Without the agent, Pocket is an app I open after a call. With it, I can ask for last week's actions, the last transcript on an account, or a question across every meeting, without exporting a PDF. Pocket's own examples are the same shape: what did I discuss last week, find the product launch talk, summarize yesterday, mark a follow-up done. Those updates write back into Pocket. I see them in the app. ## What I actually ask for In rough order of how often I do it: 1. **Drain the action list.** Open items from this week, grouped by who owns them. I close them from the same chat as I finish them. 2. **Pull context before a follow-up.** Search the account folder, fetch the last transcript, and see what was promised. That used to be ten minutes of scrolling. 3. **Find a thought I recorded weeks ago.** A ninety second memo is useless if I cannot get it back. Search is how I get it back. 4. **Ask across meetings.** On Pro, one question can come back with a combined answer and the recordings it used. I keep personal and work recordings in separate spaces and scope the question when it is a work question. Meetings themselves are on [Pocket as a meeting recorder](/pocket-meeting-recorder/). Day to day use is on [how I use Pocket](/pocket-ai-recorder/). ## What is free and what needs Pro Search, folders, account info, and action items work on every plan. Full transcripts and questions across all meetings need Pro. On the free plan, the agent can find the moment. It cannot pull the whole transcript. Do not plan a vault dump or a cross-meeting brief on search hits alone. If you want those transcripts in Obsidian, [Pocket and Obsidian](/pocket-obsidian/) is the file side. The agent can write the note. Pocket does not have to speak Obsidian for that. ## Treat it like sensitive data This server holds transcripts of conversations. It authenticates you, not the agent acting for you. That is [the gap MCP has not closed](/mcp-agent-identity-gap/). If you run it on a work machine, it belongs on whatever inventory your team keeps of connected MCP servers. I wrote about why in [shadow MCP servers](/shadow-mcp-servers/). Settings that make the recordings easier to search are on [best Pocket settings](/best-pocket-settings/). Setup, again, is not here: [Claude](/connect-pocket-ai-to-claude/) or [MCP](/pocket-mcp-server/). ## Notes from using it I will add the prompts I keep if they stay stable.