Markdownify MCP Server - UTF-8 Enhanced
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
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 based on the input source type (audio, Bing search, DOCX, file, image, PDF, PPTX, webpage, XLSX, YouTube). There is no overlap or ambiguity—each tool handles a specific format or source, making it easy for an agent to select the correct one based on the input.
All tool names follow a consistent pattern: [source]-to-markdown or get-markdown-file, using snake_case throughout. This predictable naming scheme (e.g., audio-to-markdown, pdf-to-markdown) makes the tools easy to understand and navigate, with no deviations in style.
With 10 tools, the server is well-scoped for its purpose of converting various formats to markdown. Each tool earns its place by covering a distinct input type, providing comprehensive coverage without being overwhelming or sparse for the domain.
The tool surface is complete for the server's purpose of markdown conversion, covering a wide range of common input sources (audio, documents, images, web content, videos). There are no obvious gaps; agents can handle diverse conversion tasks without dead ends or missing operations.