Connect-MCP

Docparser MCP by usefulapi

io.usefulapi/docparser · v1.0.0

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

MCPremoteno credentialsDocuments & PDFFiles & storage

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 9 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 9 tools · 6 read, 3 write (incl. delete/pay) · Documents & PDF, Files & storage

Test call docparser_ping: needs a key: HTTP 401 (1,003 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://docparser.usefulapi.io/mcp

Tools

9 tools listed at last check
  • docparser_ping Check that the connected Docparser API key works. Returns {msg: "pong"} when it does. GET /v1/ping.
  • 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_list_parser_models List the model layouts of one parser (id and label). GET /v1/parser/models/{parser_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 faile
  • 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_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_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,
  • 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 -
  • 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}.

Badge

Connect-MCP badge for io.usefulapi/docparser

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/docparser.svg)](https://clawy.uk/mcp/s/io.usefulapi/docparser)

Repository · Website