AIDataParser
PDFs, images and messy text to schema-guaranteed JSON. try_parse runs a real extraction, no key.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http aidataparser 'https://aidataparser.com/v1/mcp'
{
"mcpServers": {
"aidataparser": {
"type": "http",
"url": "https://aidataparser.com/v1/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
AIDataParser MCP server
The official Model Context Protocol registry record for AIDataParser — a credit-based data-extraction API that turns PDFs, images and messy text into schema-guaranteed JSON.
There is no server code in this repo. The MCP server is hosted: it lives at
https://aidataparser.com/v1/mcp and speaks JSON-RPC 2.0 over Streamable HTTP.
This repo holds the server.json that is the source of our record in
registry.modelcontextprotocol.io,
the canonical upstream every downstream MCP catalog syncs from.
Add it to your client
{
"mcpServers": {
"aidataparser": {
"type": "http",
"url": "https://aidataparser.com/v1/mcp",
"headers": { "Authorization": "Bearer adp_live_..." }
}
}
}
Try it before you sign up. try_parse runs a real extraction with no key,
no email and no account — up to 4,000 characters of text, 3 calls per day. Add
the server without the headers block and call it:
{ "name": "try_parse", "arguments": { "text": "INVOICE #1042 ... Total due $1,240.00", "schema_id": "invoice" } }
When you want more, get a key (50 free credits, no card) — over MCP with the
create_api_key tool, or:
curl -X POST https://aidataparser.com/v1/keys \
-H 'Content-Type: application/json' \
-d '{"email":"you@example.com"}'
Tools
| Tool | Cost | What it does |
|---|---|---|
try_parse | free, no key | Real extraction on ≤4,000 chars of text, 3/day — see the output before signing up |
create_api_key | free, no key | An email → a live adp_live_ key with 50 free credits |
parse_document | 1 credit | PDF or image (url or base64) → JSON matching your schema |
parse_text | 1 credit | Raw/messy text → JSON matching your schema |
infer_schema | 1 credit | One sample → a reusable JSON Schema |
validate | free, no key | Check a JSON value against a schema |
check_credits | free | Credits remaining on the key |
list_schemas | free, no key | Built-in templates (invoice, receipt, resume, …) |
Credit packs: https://aidataparser.com/pricing
Publishing
.github/workflows/publish-mcp.yml publishes on a push to main using GitHub
OIDC — no secrets. Bump version in server.json to cut a release; a push that
does not change the version is a no-op.
Before it publishes, the workflow runs two gates:
npm test— static checks onserver.json(validate-server-json.mjs). Each rule maps to a real failure from a sibling repo, e.g. the registry's 100-char description cap that 422'daisotools-mcp-serverv0.1.0.npm run check:remote— a liveinitialize+tools/listhandshake against the URL about to be advertised. A registry record pointing at a dead endpoint is worse than no record.
Both are runnable locally.
Frequently asked questions
What is AIDataParser?
PDFs, images and messy text to schema-guaranteed JSON. try_parse runs a real extraction, no key.
How do I install AIDataParser?
It runs as a remote server. In Claude Code: claude mcp add --transport http aidataparser 'https://aidataparser.com/v1/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does AIDataParser need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is AIDataParser open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains AIDataParser?
It is published by shibley. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.