Integrations
Meet your teams where they already work — including your AI assistant.
MCP server
Point Claude Desktop, Claude Code, or any MCP-capable enterprise copilot at DocMark and it gains a document-production arm: the assistant authors, DocMark renders, brands, and verifies. When the gate withholds a deliverable, the assistant receives the findings and can fix and resubmit in the same session.
Status: available in the self-managed options today — on-prem and your own cloud tenant. On the DocMark-managed cloud, MCP access is in private preview (available by invitation).
REST API (/v1)
A small, conventional HTTP API for any stack: submit a job, poll its status, fetch the verified artifact with its provenance record. Everything the other doors can do, scriptable from your pipeline.
Status: available in the self-managed options today — on-prem and your own cloud tenant. On the
DocMark-managed cloud, the public /v1 API is in private preview (available by invitation).
Watched folder
The zero-integration enterprise door: a shared folder on your network. Analysts drop a content file in; a verified branded deliverable (or a plain-language failure note) comes back. No SDK, no training, no workflow change — this is the intake the zero-egress tier ships with.
On the roadmap
SharePoint / OneDrive intake and a Microsoft Teams bot are under consideration — listed here as direction, not commitment, with no dates attached.