Docparser MCP by usefulapi
Run Docparser parsers: import documents by URL or upload, check status, read parsed results.
Connect it
Settings → Connectors → Add custom connector
URL: https://docparser.usefulapi.io/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://docparser.usefulapi.io/mcp{
"mcpServers": {
"docparser": {
"url": "https://docparser.usefulapi.io/mcp"
}
}
}claude mcp add --transport http docparser https://docparser.usefulapi.io/mcp{
"servers": {
"docparser": {
"type": "http",
"url": "https://docparser.usefulapi.io/mcp"
}
}
}9 tools, verified live
docparser_pingread-onlyCheck that the connected Docparser API key works. Returns {msg: "pong"} when it does. GET /v1/ping.
docparser_list_parsersread-onlyList all Document Parsers on the account (id and label). Start here: the parser id is needed by every other tool. GET /v1/parsers.
docparser_list_parser_modelsread-onlyList the model layouts of one parser (id and label). GET /v1/parser/models/{parser_id}.
docparser_get_document_statusread-onlyProcessing 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/s
docparser_get_document_resultsread-onlyThe 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_list_document_resultsread-onlyParsed 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_fetch_document_from_urlWRITE: 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 bil
docparser_upload_documentWRITE: 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. Pre
docparser_reparse_documentscan modifyWRITE: 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}.
Alternatives in Docs & Knowledge
Compare →UNUnblockedB
Unblocked is the context layer for agentic software development.
Santismm Knowledge — Harness Engineering, Agentic AI & GovernanceB
Query core AI knowledge, essays, executable Labs, Homeric data and epistemic claims.
LMLiving MemoryB
An MCP memory server. One memory your agents share — across models, devices and apps.
CECernion Energy Tools MCPB
Energy-domain MCP tools for Cernion context, evidence and guarded process preparation
LOlogrB
Query any public logr profile — timelines, events, full context — plus owner-authorized writes.
CPCenogram - Polish Real Estate Prices & Parcel DataB
Polish real estate for AI: 8M+ deed transaction prices (RCN) + per-parcel context by cadastral ID