MarkItDown MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_fileB | Convert a file to Markdown using MarkItDown |
| list_supported_formatsA | List all supported file formats for conversion |
| convert_directoryB | Convert all supported files in a directory 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 clearly distinct purpose: converting a single file, converting a directory, and listing supported formats. No overlap in functionality.
All tools follow the snake_case verb_noun pattern (convert_file, convert_directory, list_supported_formats), providing a predictable and consistent naming convention.
Three tools is appropriate for this focused server; each tool serves a necessary function and there are no redundant or missing core capabilities.
The tool set covers the primary operations for file conversion (single, batch, and format listing), though missing advanced options like output customization or conversion status checking.