MarkItDown MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MarkItDown MCP Server?

MarkItDown MCP Server is a Model Context Protocol (MCP) server that converts various file formats to Markdown using the MarkItDown utility.

how to use MarkItDown MCP Server?

To use the MarkItDown MCP Server, you can install it via Smithery or manually clone the repository and install dependencies. Once set up, it can be integrated with any MCP client to convert files to Markdown.

key features of MarkItDown MCP Server?

  • Converts multiple file formats including PDF, PowerPoint, Word, Excel, images, audio, HTML, and text-based formats to Markdown.
  • Supports integration with MCP-compliant clients like Zed Editor.
  • Provides a command-line interface for file conversion.

use cases of MarkItDown MCP Server?

  1. Converting academic papers in PDF format to Markdown for easier editing.
  2. Transforming PowerPoint presentations into Markdown for documentation purposes.
  3. Extracting text from images and audio files and converting them to Markdown format.

FAQ from MarkItDown MCP Server?

  • What file formats does MarkItDown MCP Server support?

It supports PDF, PowerPoint, Word, Excel, images, audio, HTML, and various text-based formats.

  • How do I install MarkItDown MCP Server?

You can install it via Smithery or manually by cloning the repository and installing dependencies.

  • Can I use MarkItDown MCP Server with any MCP client?

Yes, it works with any MCP-compliant client.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago