← Back to Discover

Markovo

Command-line tool and MCP server, with a hosted option, that turns supported files and authorized public web pages into Markdown through a credit-metered Markovo account.

MCP serversCommand-line tools
Visit website ↗

What it does

Markovo turns supported files and explicitly authorized public HTTPS pages into structured Markdown. This GitHub repository is the public distribution of its two client programs: the markovo command-line tool and the markovo-mcp server that runs over stdio. The repository says it contains no conversion engine or backend; conversion runs through an account-metered service at markovo.net. The clients install with pip or run on demand through uvx, and they need an API key from the developer portal. Every conversion has to carry an explicit credit ceiling, and when credits run out the service points to a billing page instead of topping up automatically. There are two ways to connect an MCP host. The remote endpoint signs in with OAuth 2.1, so no API key is shared, and it can convert a single public HTTPS page, show credits and owned jobs, and manage short-lived result-image links; it cannot read local files. The local stdio server can work with local files but is confined to one directory chosen with MARKOVO_MCP_ROOT, and the key is passed through the environment rather than as a tool argument. A REST multipart upload is also mentioned for local files. The client code is MIT licensed. The repository offers one month of Markovo Pro to anyone whose reported conversion issue is confirmed and fixed.

Capabilities

  • markovo command-line tool and markovo-mcp stdio MCP server
  • Remote MCP endpoint with OAuth 2.1 sign-in, so no API key is shared with the host
  • Local server restricted to one project directory, with symlink and parent-directory escapes rejected
  • Required credit ceiling on every conversion, with no automatic top-ups
  • Converts explicitly authorized public HTTPS pages as well as supported files
  • Install with pip or run on demand with uvx

When to use it

  • Giving a coding or research agent clean Markdown from documents and public web pages
  • Hosted agents that can connect to a remote MCP endpoint with OAuth
  • Local agent setups that need file conversion confined to a dedicated project folder
  • Teams that want spending capped on every conversion request