markpin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOW_WRITE | No | Set to enable write access; corresponds to the --allow-write flag. The server is read-only unless this is enabled. | false |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Full-text search over pages saved with Markpin (title, extracted content, clipped text, notes, tags). Returns page summaries ranked by relevance with a short snippet around the first match. With an empty query, lists the most recently updated pages (optionally filtered by tags). Summaries include readAt (when the user marked the page read) and bookmark (a reading bookmark: when it was set and, if placed inside the page, the sentence it points at). |
| get_pageA | Returns one page in full: metadata, tags, summary, the reader's one-line note ( |
| list_recentA | Lists the most recently updated pages, newest first. With bookmarked=true, lists pages with a reading bookmark, newest bookmark first. |
| list_tagsA | Lists every tag in use with the number of pages carrying it, most used first. |
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 4 tools
Each tool targets a distinct retrieval axis: recency (list_recent), relevance/full-text (search), single-page detail (get_page), and tag aggregation (list_tags). The one fuzzy boundary is that search with an empty query duplicates list_recent's behavior, but the descriptions call this out explicitly enough that an agent can still choose correctly.
Three of four tools follow a clean verb_noun pattern (list_recent, get_page, list_tags); `search` is a bare verb, a minor deviation from the pattern but unambiguous. No style mixing (camelCase vs snake_case) or chaotic variants.
Four tools is slim but proportionate for what appears to be a read-only retrieval companion to a browser bookmarking extension. Each tool covers a genuinely different access path, so none feels redundant padding, though the surface is close to thin.
The read side is thorough — pages, tags, notes, clips, reading state, and two listing orders are all reachable. However, there is no write path at all: an agent cannot save a page, add a note or clip, tag anything, or set read/bookmark state, which are the core lifecycle actions the descriptions imply exist in the underlying product.