parse-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parseA | Convert a document to markdown. Routes across backends automatically. |
| parse_urlC | Shortcut for parsing an HTTP(S) URL. Same return shape as |
| parse_to_vaultA | Parse a document and write it to the vault as a markdown note. Replaces the standalone |
| interpretA | Parse the document, then ask Claude over the parsed markdown. Use this for "summarize this PDF", "extract every action item", "what does this contract say about termination" style requests. The router parses first (cheap, deterministic), then Claude reads the markdown and answers. Cache hits across calls in the same session reuse the parsed text for free input tokens. |
| list_backendsA | Report which parse backends are installed + which are missing. Returns a list of |
| benchmarkB | Run every available backend on the same input, compare results. Diagnostic tool. Returns one ParseResult per available backend with latency, byte counts, error state, and metadata so you can see at a glance which parser handles a given document best. |
| chunk_textA | Chunk a markdown document into retrieval-ready pieces. Picks a doc-type-aware chunker (paper / book / manual / qa / resume
/ table / default) based on document structure. Set |
| detect_doc_typeA | Run structural heuristics to detect document type. Useful when you want to know what |
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 8 tools
parse, parse_url, parse_to_vault, and interpret all build on the same underlying parse operation, so an agent could easily select the wrong variant when the target or output destination is not explicitly clear. The descriptions help, but the boundaries between these tools remain somewhat fuzzy.
Most tools follow a predictable snake_case verb_noun pattern such as list_backends, chunk_text, and detect_doc_type. parse_to_vault and single-word verbs like parse, interpret, and benchmark are minor deviations, but the overall naming style is coherent.
Eight tools is well-scoped for a document parsing server with diagnostics, vault integration, and chunking support. Each tool maps to a distinct workflow need, and none feel redundant or like filler.
The toolset covers the full parse-chunk-interpret workflow, plus backend diagnostics and vault output. The main gap is the lack of a batch or multi-document parsing operation, but agents can work around that with repeated calls.