MCP Quickstart — Brand-Faithful Documents for Your AI Agent

Most “AI + PowerPoint” tools stop at generating a file. DocMark’s MCP server gives your agent something different: a brand-faithful, verified document arm. The agent writes the substance; DocMark applies your corporate brand deterministically, runs its verification gates, and hands back either the finished artifact or the findings to fix — so your agent closes the loop itself.

Availability. Runs today in the self-managed options (on-prem, your own cloud tenant). On the DocMark-managed cloud, MCP access is in private preview (by invitation) — request access.

1. Connect the server

DocMark runs a standard MCP stdio server. Add it to your MCP client’s config — for Claude Desktop / Claude Code:

{
  "mcpServers": {
    "docmark": {
      "command": "docmark-mcp",
      "env": { "DOCMARK_API_TOKEN": "<your-api-token>" }
    }
  }
}

The server is a thin client of the /v1 API — the token is the same tenant-scoped bearer token, kept control-side (never in the model’s context).

2. The tools your agent gets

• list_themes — the brands/looks available to your tenant.
• generate_deck / generate_document — submit a document job (the tool docstring teaches the strict spec + an exemplar, so the agent gets the shape right the first time).
• job_status — poll a job; a failed job returns its findings.
• fetch_result — download the verified artifact to a path.

3. The loop that makes it reliable

agent authors content  ->  generate_deck  ->  job_status
                                                 |
                         done? -> fetch_result   |  failed? -> findings
                                                 |               |
                                                 <---- fix & resubmit

When a verification gate withholds the deliverable, the agent receives why (the findings) and resubmits a corrected job — no human in the loop for the mechanical fixes. That’s the same render-then-verify discipline behind every DocMark output, exposed as a tool.

Why route your agent through DocMark

• Brand-faithful, not brand-ish — your (or your customer’s) real corporate colours, fonts, and template, applied deterministically. Per-customer branding is built in.
• Verified before delivery — the gate withholds broken output; your agent never ships a mangled slide to a client.
• Multi-format — not just slides: Word, Excel, brochures, newsletters, and narrated video from the same door. (Most MCP document tools are PPTX-only.)
• Contract-versioned — the underlying API is pinned (1.9.0), so your agent integration is stable.

Next: full API reference · deployment modes · request access