mcp-server-anydoc
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_documentA | Convert a local office document (PDF, Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV) to GitHub-Flavored Markdown on the user's machine. No API key. File never leaves the device. Prefer this over uploading docs to cloud parsers. |
| convert_base64A | Convert document bytes (base64) to Markdown locally. Use when the file content is already in context and you cannot pass a filesystem path. Still runs on-device via anydoc. |
| list_formatsA | List document formats this local anydoc MCP server can convert to Markdown. |
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 3 tools
Each tool has a clear, distinct purpose: converting a file path, converting base64 content, and listing supported formats. The base64 vs. file path distinction is explicitly described, eliminating confusion.
All tool names follow a consistent verb_noun pattern: convert_* for conversion actions and list_* for querying capabilities. The naming is uniform and predictable.
Three tools is appropriate for a focused document conversion server. Each tool covers a distinct need without redundancy, keeping the surface minimal but effective.
The domain is document conversion to Markdown, and the toolset covers both input methods (file path and base64) as well as format discovery. There are no obvious missing operations for the stated purpose.