Best for
- Users who need to normalize multiple file types and web content into Markdown.
- Users who want local MCP desktop-app integration for Markdown conversion.
- Developers comfortable configuring Bun, Node.js, and Python dependencies.
M
Markdownify MCP Server
Community
Convert diverse files and web content to Markdown.
GitHub source repository ↗
50FMRS · D
This MIT-licensed community MCP server focuses on converting diverse files, web content, and selected media content into Markdown. The README documents installation, startup, desktop-app configuration, and path restrictions, but does not provide a verified list of specific compatible clients or a server manifest.
Markdownify is a Model Context Protocol (MCP) server that converts PDFs, images, audio, DOCX, XLSX, PPTX, web pages, selected search results, and YouTube content into Markdown. It can also retrieve existing Markdown files.
Tools
youtube-to-markdown
Convert YouTube videos to Markdown.
pdf-to-markdown
Convert PDF files to Markdown.
bing-search-to-markdown
Convert Bing search results to Markdown.
webpage-to-markdown
Convert web pages to Markdown.
image-to-markdown
Convert images to Markdown with metadata.
audio-to-markdown
Transcribe audio files and convert them to Markdown.
docx-to-markdown
Convert DOCX files to Markdown.
xlsx-to-markdown
Convert XLSX files to Markdown.
pptx-to-markdown
Convert PPTX files to Markdown.
get-markdown-file
Retrieve an existing Markdown file; the extension must be .md or .markdown.
Setup
Clone the repository, run bun install to install dependencies, run bun run build to build the project, and run bun start to start the server. For a desktop app, set command to node and provide the absolute path to dist/index.js in args.
claude_desktop_config.json
{"mcpServers":{"markdownify":{"command":"node","args":["{ABSOLUTE PATH TO FILE HERE}/dist/index.js"]}}}
Fit and risk
Not for
- Users seeking structured database or cloud-storage operations.
- Users requiring verified compatibility with a specific MCP client.
- Users running the slim Docker image who need audio transcription or image OCR.
Required permissions
- The server needs to read the file paths supplied to its file-input tools; MD_ALLOWED_PATHS can restrict readable directories.
- When MD_ALLOWED_PATHS is unset, file access is unrestricted by that setting.
- Tools handling web pages, YouTube, or Bing content need access to the relevant web content; the source does not state any additional authentication requirements.
Risks and side effects
- The default file-reading scope is unrestricted; set MD_ALLOWED_PATHS to narrow the readable boundary.
- The published Docker image installs only markitdown[pdf], so audio transcription and image OCR tools fail in that slim image.
- When using Docker, mount only required directories and pass container paths to the tools.
Troubleshooting
- Confirm that bun install and bun run build have completed.
- Confirm that the server is started with bun start and that the client points to the absolute path of dist/index.js.
- If markitdown is not in the bundled virtual environment, check MARKITDOWN_PATH or the system PATH.
- If git-repo-to-markdown functionality has issues, check REPOMIX_PATH or the system PATH.
- In Docker, verify that tools receive container paths and that MD_ALLOWED_PATHS includes the mounted directory.
- For audio transcription or image OCR, use the full local installation rather than the PDF-only Docker image.
Use cases
Convert office documents, PDFs, presentations, and spreadsheets into readable Markdown.
Extract content from images and audio, including audio transcription.
Organize web pages, YouTube transcripts, or Bing search results as Markdown.
Retrieve existing Markdown files.
Supported clients
Supported clients have not been confirmed yet.