markovo-mcp
Related Servers
Alternatives to markovo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConverts various file formats to Markdown using the MarkItDown utility and can be integrated with MCP clients for seamless document processing and conversion.88MIT
- AlicenseAqualityDmaintenanceConverts files (PDF, DOCX, PPTX, XLSX, images via OCR) and URLs to Markdown, enabling AI clients to read them via a single MCP tool.1GPL 3.0
- AlicenseAqualityCmaintenanceConverts documents between Markdown, PDF, DOCX, and HTML locally with AI-friendly Markdown output and secure file access.66 npmMIT

flatmarkofficial
AlicenseNot gradedqualityBmaintenanceConverts PDF, Word, PowerPoint, Excel, and HTML documents into Markdown, handling files up to 8 MB in a single call and routing larger or scanned files through an OCR and table-detection queue that returns Markdown plus a JSON structure file. Results arrive either by polling or a signed webhook.MIT- FlicenseNot gradedqualityDmaintenanceConverts documents (PDF, DOCX, images, etc.) to Markdown using Microsoft's Markitdown library, with no local setup required. Integrates with AI agents via MCP for seamless document conversion.1-
- AlicenseNot gradedqualityCmaintenanceMCP server for converting various file formats (PDF, DOCX, images, audio, etc.) to Markdown using Microsoft MarkItDown, with support for large files and Cyrillic text.27 PyPI1MIT
TDQS
Scored across 11 tools
Each tool targets a distinct action or resource within the conversion/asset lifecycle (file vs URL conversion, job status vs assets, asset URL creation vs revocation, usage/billing/capabilities/readiness). Overlaps are minimal and descriptions clearly differentiate the few related pairs.
All tool names use the same markovo_ prefix and snake_case convention, making them predictable. A few names are noun-only (usage, billing, capabilities, doctor) rather than verb_noun, which is a minor deviation from a strict action pattern.
Eleven tools is well-scoped for a conversion and asset-delivery service. Each tool appears to earn its place, covering submission, job inspection, asset access, verification, and account diagnostics without obvious redundancy.
The surface covers the core lifecycle: conversion, job status, asset listing, asset URL creation/revocation, bundle verification, and account/diagnostic checks. Minor gaps exist around job cancellation/listing or direct bundle download/cleanup, but agents can likely work around them.