mcp server
Mdkit
Document-to-Markdown MCP server — convert PDF, Office and HTML into LLM-ready Markdown.
Description as published by the maintainer. Source
- version 1.0.0
- active
- document understanding
active — Registry entry last updated 2026-07-30. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
convert_document(filename, content_base64)- Convert a document to Markdown synchronously (the fast lane). Decode ``content_base64`` (the raw file bytes, base64-encoded) and run markitdown over it, returning ``{markdown, meta}`` where ``markdown`` is the converted text and ``meta`` carries the source ``filename`` and the output ``length`` in characters. Best for small office/HTML/text files; for large or complex documents (or OCR-heavy PDFs) use ``submit_conversion_job`` instead. Required: content_base64, filename.
get_conversion_job(job_id)- Check the status of an asynchronous conversion job you submitted. Returns ``{job_id, status, ...}`` for one of YOUR jobs (scoped to the calling identity; another caller's job id is reported as not found). When the job has ``succeeded``, small results are inlined as ``markdown`` and larger ones are returned as a ``result_url`` to fetch. A ``failed`` job includes its ``error``. Required: job_id.
submit_conversion_job(filename, webhook_url, content_base64)- Submit a document for asynchronous, high-fidelity conversion (docling). Stores the uploaded bytes, then enqueues a ``convert.docling`` job (costs 10 credits, charged now). Returns ``{job_id, status, result_url}`` — poll ``get_conversion_job`` with ``job_id`` (or supply ``webhook_url`` for a signed completion callback). Requires an API key. Raises if the docling backend is not configured for this deployment. Required: content_base64, filename.
Last successful function declaration observed on . Source: https://api.mdkit.online/mcp/. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.mdkit.online/mcp/.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-30 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-30 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.mdkit.online | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | api.mdkit.online |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json