@kazuph/mcp-pocket
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| pocket_mark_as_readA | Marks a specific Pocket article as read (archived) using its item ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
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.
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.
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.