ofd_to_text
Read OFD document
Extract the text of a Chinese OFD document (GB/T 33190: e-invoices 电子发票/数电票, official documents, bank statements) in reading order, page by page. Pass exactly one of path | url | base64.
urlpathbase64maxChars
io.github.groove79Published by GitHub account groove79v0.1.0Updated Oct 29, 2026
Read Chinese OFD documents: e-invoice (fapiao) fields, official documents, statements. No keys.
Reads Chinese OFD documents locally: full text in reading order and structured e-invoice (fapiao) fields, with no API keys.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
OFD (GB/T 33190) is China's fixed-layout document format — every e-invoice (电子发票 / 数电票), many official documents and bank statements. Most agents can't open it. This server can: text in reading order, and structured invoice fields.
Hosted (no install, pass url or base64): https://okagent.kr/api/mcp · REST https://okagent.kr/api/tools.
Pass exactly one of path, url, base64. Safe by design: only XML parts are inflated (32 MB per part, 96 MB total), XML entity declarations are refused, nothing is written.
Claude Desktop config:
Part of K-MCP. MIT.
Source: packages/ofd/README.md at commit 53af4ba
Read OFD document
Extract the text of a Chinese OFD document (GB/T 33190: e-invoices 电子发票/数电票, official documents, bank statements) in reading order, page by page. Pass exactly one of path | url | base64.
urlpathbase64maxCharsRead OFD e-invoice fields
Extract structured fields from a Chinese OFD e-invoice (发票): invoice number and code, issue date, buyer and seller name and tax ID, amount before tax, tax, total. Uses the invoice's embedded tags, else the printed labels. Pass exactly one of path | url | base64.
urlpathbase64OFD file info
Quick facts about an OFD file without the full text: title, author, creator software, creation date, page count, whether it is digitally signed, attachments, embedded tags.
urlpathbase6490% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx -y @appmonster/mcp-ofd{ "mcpServers": { "ofd": { "command": "npx", "args": ["-y", "@appmonster/mcp-ofd"] } } }