PDF/DOCX/Excel generation with stationery overlay, ZUGFeRD/XRechnung, signing, receipt OCR.
Official SDKs for the Dokmatiq DocGen API -- document generation, e-invoicing, Excel workbooks, receipt recognition, and PDF tools in a single API. Language | Package | Install | ----------|---------|---------| Java | | Maven / Gradle | Also included: MCP Server for AI assistants (any MCP client — Claude Desktop, Cursor, Continue, Cline, …) and a Claude Code Plugin (one-step install of the MCP…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Official SDKs for the Dokmatiq DocGen API -- document generation, e-invoicing, Excel workbooks, receipt recognition, and PDF tools in a single API. Language | Package | Install | ----------|---------|---------| Java | | Maven / Gradle | Also included: MCP Server for AI assistants (any MCP client — Claude Desktop, Cursor, Continue, Cline, …) and a Claude Code Plugin (one-step install of the MCP plus a triggering skill). All SDKs provide the same capabilities with idiomatic APIs: HTML, Markdown,…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.