Skip to main content
Glama
Sign In
markovo-mcp

markovo-mcp

by fisher-byte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to markovo-mcp

No user-submitted related servers found.

    Related Servers

    • docmark

      CloudCorpRecords
      A
      license
      Not graded
      quality
      B
      maintenance
      This service allows users to convert various file types (such as PDF, DOCX, and images) and web URLs into Markdown format. It functions as a local interface to a hosted document-to-Markdown conversion API.
      282 npm
      MIT

    • MarkItDown MCP Server

      courage-zen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to convert Office files, PDFs, images, archives, and other documents into Markdown over a stateless Streamable HTTP endpoint, accepting server-side paths, inline base64 content, or S3/MinIO object keys. Ships with bearer-token auth, path sandboxing, and a health probe for container and Kubernetes deployments.
      MIT

    • md-converter-mcp

      riyengar19
      A
      license
      A
      quality
      D
      maintenance
      Converts files (PDF, DOCX, PPTX, XLSX, images via OCR) and URLs to Markdown, enabling AI clients to read them via a single MCP tool.
      1
      GPL 3.0
    • flatmark

      flatmarkofficial

      flatmark-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Converts 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources