Docparser MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Docparser MCP by usefulapi is answering right now. Last checked 14 min ago. It exposes 9 tools. Last commit 12 Oct 2026.

Run Docparser parsers: import documents by URL or upload, check status, read parsed results.

Uptime history 4 hours of history

4 hours agonow

100.0%

Uptime 24h

11 of 11 checks

Tools

read from the server

145 ms

Response time

average over 24h

Stars

last commit 12 Oct 2026

Nothing serious here today

Today is the operative word: we check Docparser MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add docparser --transport http https://docparser.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "docparser": {
      "url": "https://docparser.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.docparser]
url = "https://docparser.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "docparser": {
      "url": "https://docparser.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "docparser": {
      "url": "https://docparser.usefulapi.io/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

docparser

docparser_fetch_document_from_url

WRITE: ask Docparser to download a document from a publicly reachable URL and parse it with the given parser. Uses page credits of the account's plan (documents queue when credits run out). Docparser may buy extra credits by itself only if the account owner turned on automatic credit replenishment, or the account is on an annual plan that renews early when credits run out - check the Docparser billing settings first. This server never buys credits or changes the plan. Returns the new document_id: poll docparser_get_document_status, then read docparser_get_document_results. POST /v2/document/fetch/{parser_id}.

docparser_get_document_results

The parsed data of one document (the fields and tables the parser extracted, plus file name, page count and upload/processing times). Docparser allows 60 of these calls per minute. GET /v1/results/{parser_id}/{document_id}.

docparser_get_document_status

Processing status of one document: importing/processing flags, page count, timestamps (uploaded, imported, processed), webhook dispatch and failed jobs. Poll this after a fetch/upload: the document is done when importing_in_progress and processing_in_progress are false, processed_at is set and failed_jobs is empty (a non-empty failed_jobs means it failed); then read the results. GET /v2/document/status/{parser_id}/{document_id}.

docparser_list_document_results

Parsed data of several documents of one parser: the last uploaded ones (default), or those uploaded/processed after a date. Returns up to 100 documents per call; page with offset (next_offset is null on the last page). Docparser allows 30 of these calls per minute. GET /v1/results/{parser_id}.

docparser_list_parser_models

List the model layouts of one parser (id and label). GET /v1/parser/models/{parser_id}.

docparser_list_parsers

List all Document Parsers on the account (id and label). Start here: the parser id is needed by every other tool. GET /v1/parsers.

docparser_ping

Check that the connected Docparser API key works. Returns {msg: "pong"} when it does. GET /v1/ping.

docparser_reparse_documents

WRITE: run the parser again over already imported documents (for example after changing parsing rules). Replaces their parsed data. Re-parsing documents already in the account does not use additional credits. 1-50 document ids per call. POST /v1/document/reparse/{parser_id}.

docparser_upload_document

WRITE: upload one small file as base64 content to a parser and parse it. Uses page credits of the account's plan. Docparser may buy extra credits by itself only if the account owner turned on automatic credit replenishment, or the account is on an annual plan that renews early when credits run out - check the Docparser billing settings first. This server never buys credits or changes the plan. Prefer docparser_fetch_document_from_url for large files. Returns the new document id and the remaining quota. POST /v1/document/upload/{parser_id}.

Endpoints

URL	Transport	State	Latency	Checked
https://docparser.usefulapi.io/mcp	streamable-http	answering	87 ms	14 min ago

Alternatives to Docparser MCP by usefulapi

same job, measured the same way

Onfido MCP by usefulapi

by usefulapi

Create and read Onfido applicants, documents, checks and reports.

14 tools answering

Documenso MCP by usefulapi

by usefulapi

Read and send documents for signature — templates, recipients, fields and folders.

16 tools answering

Metriport MCP by usefulapi

by usefulapi

Read and write patients, facilities, medical documents, and consolidated FHIR records in Metriport.

12 tools answering

Paperform MCP by usefulapi

by usefulapi

Read Paperform forms, submissions, products and coupons, Papersign documents, and manage coupons.

23 tools answering

Paperless MCP

by pvliesdonk

Paperless-NGX over MCP: search, read, upload and tag documents; manage correspondents and types.

275 installs/wk local only

PDFSpark MCP

by dpozimski

Convert HTML or URLs to PDF documents powered by Playwright

27 installs/wk local only

Taggun MCP by usefulapi

by usefulapi

Scan receipts with Taggun OCR from a URL or file and read receipt-validation campaigns.

6 tools answering

Google Docs MCP

by a1-x-tech

MCP server for the Google Docs API: read and edit documents, styles, tables, images, comments.

50 installs/wk local only

Docparser MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Docparser MCP by usefulapi do?

It exposes 9 tools, read directly from the server on our last check. Among them: docparser_fetch_document_from_url, docparser_get_document_results, docparser_get_document_status, docparser_list_document_results, docparser_list_parser_models, docparser_list_parsers and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Docparser MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 11 of 11 checks got a reply (100.0%), average response time 145 ms. The bar chart above shows every period we have measured.

How do I connect Docparser MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Docparser MCP by usefulapi need an API key?

No. Docparser MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Docparser MCP by usefulapi?

It answers our handshake in 145 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Docparser MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.