Pulpie MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PULPIE_URL | No | Where the backend runs. Only local URLs get auto-started. | http://127.0.0.1:8787 |
| PULPIE_HOME | No | Holds the global library and `backend.log`. | ~/.pulpie |
| PULPIE_LIBRARY | No | Where saved docs go when no directory is given. | $PULPIE_HOME/library |
| PULPIE_IDLE_TIMEOUT | No | Seconds without requests before the backend exits. `0` keeps it running. | 1800 |
| PULPIE_ALLOW_PRIVATE | No | Set to `1` to allow `localhost` and LAN addresses. By default the server won't fetch `localhost`, `127.0.0.1`, LAN addresses like `192.168.x.x`, or cloud metadata addresses. | off |
| PULPIE_START_TIMEOUT | No | How long to wait for the backend to start. The first run includes the model download. | 600 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_markdownA | Fetch a web page and return its main content as Markdown, without saving it. |
| save_markdownB | Fetch a web page and save its main content as a Markdown file. Returns the path and outline. |
| crawl_docsB | Crawl a documentation site and save every page as Markdown, plus an index.md. |
| list_libraryB | List Markdown docs saved by pulpie, with their source URL and fetch time. |
| search_libraryA | Search saved docs by content. Returns the best matching sections with their file paths. |
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 5 tools
fetch_markdown and save_markdown are the only pair with overlapping purposes, but the save/no-save distinction is clearly stated. list_library, search_library, and crawl_docs each target a distinct operation with no real ambiguity.
All five tools follow a clean verb_noun snake_case pattern (fetch_markdown, save_markdown, crawl_docs, list_library, search_library). The convention is applied uniformly and reads predictably.
Five tools is a tight, well-scoped set for a fetch/save/search docs server. Each tool earns its place with no redundancy.
The lifecycle covers fetch, persist, bulk-crawl, browse, and search. Minor gaps exist: no tool to delete or remove a saved doc, and no direct read of a specific saved file, but these are workaroundable.