MCPSERV.CLUB
kazuph

MCP Pocket

MCP Server

Fetch and manage your Pocket articles via Claude Desktop

Stale(65)
9stars
1views
Updated May 28, 2025

About

MCP Pocket is a Node.js MCP server that lets Claude Desktop users retrieve their saved Pocket articles and mark them as read. It provides simple commands for fetching article metadata and archiving items directly from the desktop.

Capabilities

Resources
Access data sources
Tools
Execute functions
Prompts
Pre-built templates
Sampling
AI model interactions

MCP Pocket Server Badge

Overview

MCP Pocket is a lightweight connector that bridges Claude Desktop (or any MCP‑compatible client) with the Pocket API, allowing developers to seamlessly integrate personal article collections into AI workflows. By exposing Pocket’s data through MCP tools, the server solves the common problem of pulling contextual content from a user‑managed reading list into an AI assistant without manual API handling or authentication management.

The server adds two intuitive MCP tools: and . The former retrieves a curated list of the user’s saved items, delivering each article’s title, URL, and an excerpt that can be fed directly into Claude for summarization, research assistance, or content curation. The latter lets the assistant archive items on behalf of the user, enabling a smooth “read it later” workflow where Claude can recommend articles and then automatically mark them as read once the user has finished. This tight coupling of fetch and update actions keeps the Pocket library in sync with the AI’s interactions.

For developers, MCP Pocket offers a plug‑and‑play integration: after installing the package and supplying Pocket credentials via environment variables, the server registers its tools in the client’s configuration. No additional code is required to call these tools; a single MCP command suffices. This simplicity lets teams prototype AI‑driven reading assistants, build recommendation engines, or embed Pocket data into broader knowledge‑management systems without wrestling with OAuth flows or HTTP client setup.

Typical use cases include:

  • Personal knowledge bases – Claude can pull recent articles into a personal wiki or note‑taking app, summarizing key points and tagging them for future reference.
  • Research assistants – A researcher can ask Claude to fetch the latest saved papers, then have the assistant organize them by topic or citation style.
  • Content curation bots – Social media managers can let an AI compile a weekly digest of saved articles, automatically marking them as read after posting.
  • Study aids – Students can query Claude for their Pocket reading list and receive concise study notes or flashcards generated on the fly.

MCP Pocket’s standout advantage is its zero‑friction authentication: credentials are passed through environment variables, and the server handles all Pocket API interactions internally. This reduces security risks compared to embedding keys in client code and keeps the integration lightweight, making it ideal for rapid prototyping or production deployments where privacy and simplicity are paramount.