Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Run Docparser parsers: import documents by URL or upload, check status, read parsed results.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://docparser.usefulapi.io/mcpRun this in your terminal
claude mcp add --transport http docparser https://docparser.usefulapi.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"docparser": {
"url": "https://docparser.usefulapi.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"docparser": {
"type": "http",
"url": "https://docparser.usefulapi.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://docparser.usefulapi.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.
docparser_pingCheck that the connected Docparser API key works. Returns {msg: "pong"} when it does. GET /v1/ping.
docparser_list_parsersList 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_modelsList the model layouts of one parser (id and label). GET /v1/parser/models/{parser_id}.
docparser_get_document_statusProcessing 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_resultsThe 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_resultsParsed 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_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 cr
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 wh
docparser_reparse_documentsWRITE: 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}.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 44 ms (HTTP 200)
No sign-in needed
Read 9 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.23.2) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Use Docparser from Claude, Cursor, or any MCP client — list parsers, import documents, poll their status and read the parsed data. Hosted, no local install: connect with your own Docparser credentials.
Live endpoint: https://docparser.usefulapi.io/mcp · Homepage: https://usefulapi.io/docparser
https://docparser.usefulapi.io/mcp.claude mcp add --transport http docparser https://docparser.usefulapi.io/mcp, then run /mcp to log in.{
"mcpServers": { "docparser": { "url": "https://docparser.usefulapi.io/mcp" } } }
Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Docparser credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/docparser/
| Tool | Type | What it does |
|---|---|---|
docparser_ping | read | Check API key |
docparser_list_parsers | read | List parsers |
docparser_list_parser_models | read | List parser model layouts |
docparser_get_document_status | read | Get document status |
docparser_get_document_results | read | Get parsed data of one document |
docparser_list_document_results | read | List parsed data of many documents |
docparser_fetch_document_from_url | write | Import a document from a URL |
docparser_upload_document | write | Upload a document (base64) |
docparser_reparse_documents | write | Re-parse documents |
docparser_usage_status | meta | Usage status (free-tier meter) |
docparser_request_feature | meta | Request a missing feature |
docparser_upgrade | meta | Upgrade to Pro or Pro+ |
docparser_cancel_subscription | meta | Cancel the Pro subscription |
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro (per user) | $9/mo or $90/yr (2 months free) | Unlimited* |
\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.
Pro covers this server only. Subscribe with docparser_upgrade (it returns a Stripe Checkout link). Cancel any time with docparser_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running docparser_upgrade before then undoes the cancel. Or write to support@usefulapi.io.
MIT © usefulapi. Not affiliated with or endorsed by Docparser.