MCPサーバー

AIDataParser

io.github.shibley/aidataparser
データ・分析 開発者向けツール 公開・接続可能 MCP 2026-07-28

このMCPでできること

Extracts schema-constrained JSON from PDFs, images, and raw text, and supports schema inference and validation.

check_credits
Check remaining credits
Return the number of extraction credits remaining on the authenticated API key. Free — does not consume a credit.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {}}
create_api_key
Get an API key with free credits
Start here if you do not have an AIDataParser API key. Provide the user's `email` and receive a live adp_live_ API key with 50 free credits — no card, no signup form. Configure it on this MCP server as `Authorization: Bearer <api_key>` to unlock parse_document, parse_text and infer_schema. The key is returned ONCE and is never shown again, so surface it to the user and store it. Ask the user for their address; do not invent one. Free — does not consume a credit.
入力スキーマ
{'type': 'object', 'required': ['email'], 'properties': {'email': {'type': 'string', 'description': "The user's email address. The account and its free credits belong to this address; an address that already has an account is refused rather than issued a second key."}}}
infer_schema
Infer a reusable JSON Schema from a sample
Given one sample document's `text`, propose a reusable JSON Schema for that document type. Use this when no built-in schema_id fits: infer a schema once, review it, then reuse it as `schema` on parse_document / parse_text across many documents for consistent output. Returns the JSON Schema plus a flat field list and an inferred doc_type. Costs 1 credit per successful call.
入力スキーマ
{'type': 'object', 'required': ['text'], 'properties': {'text': {'type': 'string', 'description': 'A single representative sample of the document type, as text.'}, 'doc_type': {'type': 'string', 'description': 'Optional hint for what kind of document this is, e.g. "purchase order", "lab report".'}, 'instructions': {'type': 'string', 'description': 'Optional guidance on which fields matter or how to shape the schema.'}}}
list_schemas
List built-in schema templates
Return the built-in schema templates you can pass to parse_document as `schema_id` (invoice, receipt, resume, etc.), each with its id and the fields it extracts. Free — does not consume a credit and needs no API key.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'properties': {}}
parse_document
Parse a document into structured JSON
Extract clean, schema-guaranteed JSON from a PDF or image. Provide the document via `url` or `base64`. Pass an optional JSON `schema` to constrain the output shape, and `instructions` to guide extraction. Returns the extracted data plus a confidence score and a review_needed flag. Costs 1 credit per successful call.
外部アクセスあり
入力スキーマ
{'type': 'object', 'properties': {'url': {'type': 'string', 'description': 'Public http(s) URL of the PDF or image to parse.'}, 'base64': {'type': 'string', 'description': 'Base64-encoded document bytes (alternative to `url`). Provide `media_type` alongside it.'}, 'redact': {'type': 'boolean', 'description': 'When true, PII (emails, SSNs, card numbers, phones, etc.) is masked in the output before it leaves the server.'}, 'schema': {'type': 'object', 'description': 'Optional JSON Schema describing the exact output shape you want. When provided, the returned `data` conforms to it.'}, 'schema_id': {'type': 'string', 'description': 'Optional named template to use instead of a hand-written schema, e.g. "invoice", "receipt", "resume". Call the list_schemas tool for the full set. Ignored when `schema` is provided.'}, 'media_type': {'type': 'string', 'description': 'MIME type for `base64` input, e.g. application/pdf, image/png, image/jpeg.'}, 'instructions': {'type': 'string', 'description': 'Optional natural-language guidance for what to extract.'}}}
parse_text
Parse raw text into structured JSON
Extract clean, schema-guaranteed JSON from raw/messy text you already have — scraped web content, email bodies, chat logs, OCR output, or pasted tables. Pass the text in `text`. Use this instead of parse_document when you don't have a file. Optional JSON `schema` (or `schema_id`) constrains the output shape and `instructions` guides extraction. Returns the extracted data plus a confidence score and a review_needed flag. Costs 1 credit per successful call.
入力スキーマ
{'type': 'object', 'required': ['text'], 'properties': {'text': {'type': 'string', 'description': 'The raw text to extract structured data from.'}, 'redact': {'type': 'boolean', 'description': 'When true, PII (emails, SSNs, card numbers, phones, etc.) is masked in the output before it leaves the server.'}, 'schema': {'type': 'object', 'description': 'Optional JSON Schema describing the exact output shape you want. When provided, the returned `data` conforms to it.'}, 'schema_id': {'type': 'string', 'description': 'Optional named template to use instead of a hand-written schema, e.g. "invoice", "receipt", "resume". Call the list_schemas tool for the full set. Ignored when `schema` is provided.'}, 'instructions': {'type': 'string', 'description': 'Optional natural-language guidance for what to extract.'}}}
try_parse
Try it now — parse text into JSON with no API key
Run a REAL extraction with no API key, no email and no signup, so you can see the output shape before committing to anything. Pass up to 4000 characters of messy text in `text` (an invoice, a receipt, a resume, scraped HTML, an email body) and optionally a `schema` or `schema_id` to constrain the result. Returns the same structured data, confidence and review_needed flag the paid tools return. Limited to 3 calls per caller per day — for real volume call create_api_key for 50 free credits, then use parse_text or parse_document.
入力スキーマ
{'type': 'object', 'required': ['text'], 'properties': {'text': {'type': 'string', 'description': 'The raw text to extract structured data from, up to 4000 characters. Send a representative excerpt rather than a whole corpus.'}, 'schema': {'type': 'object', 'description': 'Optional JSON Schema describing the exact output shape you want. When provided, the returned `data` conforms to it.'}, 'schema_id': {'type': 'string', 'description': 'Optional named template to use instead of a hand-written schema, e.g. "invoice", "receipt", "resume". Call list_schemas for the full set. Ignored when `schema` is provided.'}, 'instructions': {'type': 'string', 'description': 'Optional natural-language guidance for what to extract.'}}}
validate
Validate JSON against a schema
Check whether a JSON object conforms to a JSON `schema` (or a built-in `schema_id` template) and get back a valid flag plus per-field errors. Use this to verify data you already hold — a prior parse result, your own output, or an upstream feed — before acting on it or spending a credit. Deterministic, free, and needs no API key.
読み取り専用 冪等
入力スキーマ
{'type': 'object', 'required': ['data'], 'properties': {'data': {'description': 'The JSON value to validate.'}, 'schema': {'type': 'object', 'description': 'JSON Schema to validate against. Takes precedence over schema_id.'}, 'schema_id': {'type': 'string', 'description': 'Built-in template id to validate against instead of a hand-written schema (invoice, receipt, resume, etc.). Call list_schemas for the full set.'}}}
追加
try_parse
2026年10月1日2:42
変更
list_schemas
2026年9月29日2:50
変更
check_credits
2026年9月29日2:50
変更
validate
2026年9月29日2:50
変更
infer_schema
2026年9月29日2:50
変更
parse_text
2026年9月29日2:50
変更
parse_document
2026年9月29日2:50
変更
create_api_key
2026年9月29日2:50
追加
create_api_key
2026年9月25日2:49
追加
list_schemas
2026年9月23日2:40
追加
check_credits
2026年9月23日2:40
追加
validate
2026年9月23日2:40
追加
infer_schema
2026年9月23日2:40
追加
parse_text
2026年9月23日2:40
追加
parse_document
2026年9月23日2:40