Markdownify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UV_PATH | No | The path to the uv executable. By default, the server will use the default install location of uv. | |
| MD_SHARE_DIR | No | Optional path to restrict the directory from which Markdown files can be retrieved |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audio-to-markdownC | Convert an audio file to markdown, including transcription if possible |
| bing-search-to-markdownC | Convert a Bing search results page to markdown |
| docx-to-markdownC | Convert a DOCX file to markdown |
| get-markdown-fileC | Get a markdown file by absolute file path |
| image-to-markdownC | Convert an image to markdown, including metadata and description |
| pdf-to-markdownC | Convert a PDF file to markdown |
| pptx-to-markdownC | Convert a PPTX file to markdown |
| webpage-to-markdownC | Convert a webpage to markdown |
| xlsx-to-markdownC | Convert an XLSX file to markdown |
| youtube-to-markdownC | Convert a YouTube video to markdown, including transcript if available |
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 10 tools
Every tool has a clearly distinct purpose focused on converting a specific input type (audio, Bing search, DOCX, etc.) to markdown. There is no ambiguity or overlap in functionality—each tool targets a unique source format, making tool selection straightforward for an agent.
All tool names follow a consistent pattern of 'source-to-markdown' (e.g., audio-to-markdown, docx-to-markdown). This uniform verb_noun style is predictable and readable, with no deviations in naming conventions across the set.
With 10 tools, the server is well-scoped for its purpose of converting various file types and sources to markdown. Each tool earns its place by covering a distinct input format, and the count is neither too sparse nor overwhelming for the domain.
The tool set provides comprehensive coverage for converting common file types (DOCX, PDF, PPTX, XLSX, image, audio) and sources (webpage, YouTube, Bing search) to markdown. There are no obvious gaps—it supports a complete workflow for markdown conversion from diverse inputs.