# Docparser Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Docparser

Extract structured data from documents like invoices, receipts, and forms using AI-powered parsing.

- Record: https://musedirectory.ai/connector/docparser
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/docparser/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 3209ms, checked 2026-10-29T10:45:47Z
- Endpoint: https://docparser.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T07:56:41Z)
- Source: Found in the official MCP Registry (io.usefulapi/docparser) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fdocparser

Connects to Docparser to upload or fetch documents, run custom parsers to extract fields and tables, and retrieve parsed results. Muse can help you process documents, track parsing status, and organize extracted data.

Example request: "Upload an invoice and extract the vendor name, invoice number, and total amount."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Docparser to help me. It is a free service with an MCP server at https://docparser.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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
- 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/result
- 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 cr
- 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 wh
- 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}.

Screening checks:
- MCP handshake: pass (Answered in 10ms)
- Domain against threat feeds (Cloudflare security DNS): pass (docparser.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (9 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)