MCP Pocket MCP Server

🔗 Model Context Protocol (MCP) Server for retrieving saved articles from Pocket API and loading them into Claude

Local serverstdioTypeScript

What is the MCP Pocket MCP server?

Connect MCP Pocket to Claude, Cursor or any other MCP client and it stops being a tab you switch to. 🔗 Model Context Protocol (MCP) Server for retrieving saved articles from Pocket API and loading them into Claude. The mcp pocket mcp server is what makes that connection.

What the server does

This is a connector to allow Claude Desktop (or any MCP client) to fetch your saved articles from Pocket API.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • pocket_get_articles — Fetch your saved articles from Pocket API. Returns title, URL, and excerpt for each article
  • pocket_mark_as_read — Mark a specific article as read (archived) in your Pocket account using its item ID

Credentials and setup notes

Configuration is passed through the environment: POCKET_CONSUMER_KEY, POCKET_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Pocket's toolset — pocket_get_articles, pocket_mark_as_read — is a fair guide to whether it matches your workflow. It is maintained by kazuph; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
pocket_get_articlesFetch your saved articles from Pocket API. Returns title, URL, and excerpt for each article.
pocket_mark_as_readMark a specific article as read (archived) in your Pocket account using its item ID.

How to install the MCP Pocket MCP server

{
  "mcpServers": {
    "pocket": {
      "command": "npx",
      "args": ["-y", "@kazuph/mcp-pocket"],
      "env": {
        "POCKET_CONSUMER_KEY": "your-pocket-consumer-key",
        "POCKET_ACCESS_TOKEN": "your-pocket-access-token"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
POCKET_CONSUMER_KEYCredential the server authenticates with.Yes
POCKET_ACCESS_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Pocket to pocket get articles.
  • Use MCP Pocket to pocket mark as read.

Frequently asked questions

Node.js, Claude Desktop (or another MCP client), and Pocket API credentials (consumer key and access token) are required.