Mcp Jp Doc Intel
Extract structured fields from Japanese invoices and business cards via a hosted document-intelligence API inside agent workflows.
Overview
io.github.infoinlet-marketplace/mcp-jp-doc-intel is a MCP server for the Build phase that calls a hosted API to OCR and classify Japanese invoices and business cards for AI agents.
What is this MCP server?
- Japanese invoice (請求書) extraction for accounting and ops automation
- Meishi (business card) capture and structured field output
- OCR and document classification via hosted API
- Stdio MCP @infoinlet/mcp-jp-doc-intel v0.1.0 on npm
- Targets JP-market solo products without building custom vision pipelines
- Document types named: invoice and meishi (business card)
- npm package version 0.1.0
- Hosted API architecture stated in description
What problem does it solve?
Solo builders targeting Japan waste weeks on handwritten OCR pipelines for invoices and meishi layouts agents cannot parse from raw PDFs alone.
Who is it for?
Indie developers shipping JP-language SaaS, back-office tools, or CRM intake that must read invoices and meishi reliably.
Skip if: Global English-only document pipelines or teams that refuse hosted document APIs for compliance reasons.
What do I get? / Deliverables
After you configure API credentials and the MCP server, your agent can return structured extraction results from Japanese business documents in workflow steps.
- Structured fields from JP invoices and meishi via agent tool calls
- OCR and classification outputs suitable for downstream database inserts
Recommended MCP Servers
Journey fit
Japanese document MCP is categorized under Build integrations because it wires a regional OCR and classification API into the product you are shipping. Integrations is the right shelf for hosted doc-intel APIs that agents call instead of bespoke parsing scripts.
How it compares
Region-specific hosted doc-intel MCP, not a general filesystem reader or spreadsheet skill.
Common Questions / FAQ
Who is io.github.infoinlet-marketplace/mcp-jp-doc-intel for?
Solo builders and small teams automating Japanese invoice and business-card intake with AI agents and a hosted document API.
When should I use io.github.infoinlet-marketplace/mcp-jp-doc-intel?
Use it while integrating JP document upload flows, expense tooling, or CRM capture where OCR and classification must understand local formats.
How do I add io.github.infoinlet-marketplace/mcp-jp-doc-intel to my agent?
Install @infoinlet/mcp-jp-doc-intel, add the stdio MCP server to your client, and configure the hosted API keys and endpoints required by the service README.