Ext Ops Panel
Open dashboard
Comparison

Obsidian vs Markovo File to Markdown

Obsidian is an MCP server published by MarkusPfundstein. Marketplaces we read that list it: 1 (Docker MCP Catalog). Markovo File to Markdown is an MCP server published by fisher-byte. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceObsidianMarkovo File to Markdown
Docker MCP Catalog Listed
Version: sha256:0eba4c05742a
Forks (GitHub): 506
Pulls (Docker Hub): 142 760
Stars (Docker Hub): 31
Stars (GitHub): 4 477
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (PyPI): 53
Downloads/week (PyPI): 14
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Obsidian vs Markovo File to Markdown
FactObsidianMarkovo File to Markdown
Marketplaces that list it11
Stars (GitHub) (differs)4 477 (better)0 (worse)
Pulls (Docker Hub) (differs)142 760No figure on Docker Hub
Forks (GitHub) (differs)506 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/obsidian)Remote server (markovo.net/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)12Not published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/markuspfundstein/mcp-obsidiangithub.com/fisher-byte/markovo
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Obsidian

In its own words, on Docker MCP Catalog:

MCP server that interacts with Obsidian via the Obsidian rest API community plugin.

Markovo File to Markdown

In its own words, on Official MCP Registry:

Convert files and authorized public HTTPS pages to Markdown with secure job and billing guidance.

How to run each

Obsidian As a local MCP server: Docker image

Claude Code
claude mcp add --env "OBSIDIAN_API_KEY=<YOUR_OBSIDIAN_API_KEY>" --transport stdio obsidian -- docker run -i --rm -e OBSIDIAN_API_KEY mcp/obsidian

Requires: OBSIDIAN_API_KEY (secret)

Markovo File to Markdown As a remote MCP server

Claude Code
claude mcp add --transport http markovo https://markovo.net/mcp

Requires: MARKOVO_API_KEY (secret), MARKOVO_MCP_ROOT

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Markovo File to Markdown has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Markovo File to Markdown publish no list of tools, so we do not compare tools.

Settings each asks for

Only Obsidian asks for

  • OBSIDIAN_API_KEY (secret)
  • OBSIDIAN_HOST

Only Markovo File to Markdown asks for

  • MARKOVO_API_KEY (secret)
  • MARKOVO_MCP_ROOT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Obsidian · What it can do: Markovo File to Markdown · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built