md-converter-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_to_markdownA | Convert a file or URL to Markdown. Supports PDF, DOCX, PPTX, XLSX/XLS, images (OCR via Tesseract), and web pages. Automatically logs token savings to a local database — view the dashboard at http://localhost:3847. Pass an absolute file path or an HTTP/HTTPS URL. |
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 1 tool
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clear and distinct.
The single tool name 'convert_to_markdown' follows a clear verb_noun pattern and is descriptive. Consistency is trivially maintained with one tool.
The server has exactly one tool, which feels borderline for a converter that supports many formats. While it could be sufficient, a single tool may limit flexibility for advanced use cases.
The tool covers the primary domain of converting various file types and URLs to Markdown, including OCR and web pages. No obvious gaps in the conversion workflow are apparent.