Skip to main content
Glama
Sign In
enesjakozh
@kazuph/mcp-pocket

@kazuph/mcp-pocket

by kazuph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

MCP 口袋

这是一个连接器，允许 Claude Desktop（或任何 MCP 客户端）从 Pocket API 获取您保存的文章。

先决条件

Related MCP server: Notion MCP

快速入门

  1. 修改位于此处的 Claude Desktop 配置： ~/Library/Application\ Support/Claude/claude_desktop_config.json

您可以通过 Claude Desktop 菜单轻松找到它：

  1. 打开 Claude 桌面

  2. 在 Mac 菜单栏上单击 Claude

  3. 点击“设置”

  4. 点击“开发者”

如果您没有此配置，您可以在此位置创建一个空文件。

将以下内容添加到配置文件中，用您自己的凭据替换：

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

开发设置

  1. 克隆此存储库并安装依赖项：

git clone https://github.com/kazuph/mcp-pocket.git
cd mcp-pocket
npm install

  1. 对于开发，请使用此配置：

{
  "mcpServers": {
    "pocket": {
      "command": "npx",
      "args": ["tsx", "/path/to/mcp-pocket/index.ts"],
      "env": {
        "POCKET_CONSUMER_KEY": "your-pocket-consumer-key",
        "POCKET_ACCESS_TOKEN": "your-pocket-access-token"
      }
    }
  }
}

开发命令

# Build TypeScript
npm run build

# Watch mode for development
npm run watch

# Publish to npm
npm login
npm publish

可用命令

Claude Desktop 中将提供以下 MCP 工具：

  • pocket_get_articles ：从 Pocket API 获取已保存的文章。返回每篇文章的标题、URL 和摘录。

  • pocket_mark_as_read ：使用其项目 ID 将特定文章标记为已读（已存档）。

获取 Pocket API 凭证

有关获取 Pocket API 凭证的详细说明，请参阅问题 #2 。

快速步骤：

  1. 在Pocket Developer Portal上创建新应用程序

  2. 按照身份验证流程获取您的消费者密钥和访问令牌

执照

麻省理工学院

Available Tools

2 tools
pocket_get_articlesA

Fetches the latest unread articles from Pocket API. Returns up to 20 articles by default. You can specify the number of articles to fetch (1-20) using the count parameter. Returns the article ID, title, URL, and excerpt for each article.

Inputs: count.

pocket_mark_as_readA

Marks a specific Pocket article as read (archived) using its item ID.

Inputs: itemId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one fetches unread articles, while the other marks articles as read. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the desired action.

    Naming Consistency5/5

    Both tools follow a consistent 'pocket_verb_noun' pattern, using snake_case and starting with the server domain prefix. This predictability aids in tool identification and usage.

    Tool Count2/5

    With only two tools, the server feels thin for a Pocket API integration. While it covers fetching and marking articles, it lacks operations like adding articles, managing tags, or retrieving read articles, which are core to the Pocket domain.

    Completeness2/5

    The toolset is severely incomplete for a Pocket API server. It misses essential operations such as adding articles to Pocket, retrieving read articles, managing tags, and deleting articles, leaving significant gaps that will hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches