MCP100 IndexMCP Server
WatchlistCommunity implementation

Markdownify MCP Server

by Zac Aceres

Reviewed October 5, 2026

MCP Server

Watchlist tracking

Reviewed for relevance and future tracking value.

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track converter formats and extraction behavior as input sources change

Reviewed · Documentation review; complete setup workflow not independently tested

Best fit

Converting local documents, media and web content into Markdown for AI workflows.

What we know

Markdownify MCP wraps document/media conversion tools so MCP clients can turn local files and web content into Markdown.

Maintenance / activity evidence

  • Observed (UTC)1.1.0

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

  • Installation and comprehensive security have not been independently audited.
  • Can read local files and fetch external web/media content. Writes: Produces converted outputs.
  • Authentication not yet verified.
  • Sensitive access: Local documents, Images/audio, Potentially private files
  • Local document access is the main boundary; configure allowed paths or read-only mounts to avoid exposing unrelated files.
  • Use MD_ALLOWED_PATHS or read-only container mounts to constrain file access.
Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

3,000 repository stars

Stars observed Oct 6, 2026.

Package download provider did not return a stable package record during this audit; do not publish a 30-day download number yet.

Package download provider did not return a stable package record during this audit; do not publish a 30-day download number yet.

Package download provider did not return a stable package record during this audit; do not publish a 30-day download number yet.

All limitations / Review context

Which file and web formats are currently handled by Markdownify MCP?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

  • Local document access is the main boundary; configure allowed paths or read-only mounts to avoid exposing unrelated files.
  • Use MD_ALLOWED_PATHS or read-only container mounts to constrain file access.
  • Can read local files and fetch external web/media content.
  • Local documents and fetched web content are processed by the running server.
  • Reviewed write actions: Produces converted outputs
  • Sensitive access: Local documents, Images/audio, Potentially private files
  • Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
  • A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
  • No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
  • The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
  • Comparable package-download metric
  • Some conversion features require optional Python extras.
  • Local file-path restrictions are optional and should be configured explicitly.

Original activity observations

  • 2026-05-01T21:05:09Z: 1.1.0
Technical identity
github.com/zcaceres/markdownify-mcp
Reviewed resource type
MCP Server
Repository identity
zcaceres/markdownify-mcp

Evidence & Sources

Evidence basis
Recorded source evidence
Setup runtime verification
Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed · Latest source observation