Integration

LayerOne DocX integration

LayerOne DocX generates PDF and DOCX documents from Word templates: store a .docx template with variables, fill it with JSON data and get the finished file back, or produce Factur-X invoices (PDF/A-3 with embedded EN 16931 XML, the French B2B e-invoicing format) from a template or from an existing PDF. Templates are versioned: list, download and restore earlier versions. Each API key has a monthly quota on a rolling 30-day cycle (free plan 20 documents, Starter 500, Pro 5,000, or unlimited); check it with get_usage_stats, a 429 means the quota or the rate limit is reached. Not exposed: listing stored templates, images and signature files injected into templates, the electronic signature routes, and the account and key management routes. Authentication is an API key created in the LayerOne console (dev.layerone.fr), sent in the X-API-Key header.

Connect LayerOne DocX How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in LayerOne DocX.Built from the 11 LayerOne DocX tools below, on the connection you add once.

What you can do with LayerOne DocX

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Template, 4 operations

create_templateCreate templatePOSTStores a Word (.docx) template once so later renders can pass its template_id instead of re-sending the file. Returns the template_id and the variables detected in the file.
delete_templateDelete templateDELETEPermanently deletes a stored template together with all its archived versions. Cannot be undone.
download_templateDownload templateGETDownloads the current Word (.docx) file of a stored template.
replace_templateReplace templatePUTReplaces the file of a stored template with a new .docx version, for real. The previous content is archived first when it differs, so it can be listed with list_template_versions and restored.

Version, 2 operations

download_template_versionDownload template versionGETDownloads the Word (.docx) content of one archived version of a template. 404 when the version does not exist or access is refused.
list_template_versionsList template versionsGETLists the archived versions of a stored template (without their content), newest version first. 404 when the template does not exist or does not belong to the API key.

Attach facturx, 1 operation

attach_facturxAttach facturxPOSTConverts an already laid out invoice PDF into a Factur-X PDF (PDF/A-3 with the EN 16931 XML derived from json_data attached), without a template. Counts against the monthly quota.

Render document, 1 operation

render_documentRender documentPOSTFills a Word template with JSON data and returns the finished PDF (default) or DOCX file. Pass a stored template_id or upload the template file. Counts against the monthly quota.

Render facturx, 1 operation

render_facturxRender facturxPOSTLike render_document but returns a Factur-X invoice PDF (PDF/A-3 with generated EN 16931 XML), the French B2B e-invoicing format. Pass template_id or a template file. Counts against the monthly quota.

Restore, 1 operation

restore_template_versionRestore template versionPOSTMakes an archived version (version_id from list_template_versions) the active content of the template; the current content is archived first, so it can be undone. 404 for an unknown version.

Usage stats, 1 operation

get_usage_statsGet usage statsGETReturns the API key's plan, monthly quota (limit, used, remaining), rate limit and current usage counters. The quota resets on a rolling 30-day cycle from the subscription date, not on the 1st.

Use LayerOne DocX from Claude Code, Cursor or Codex

Connect LayerOne DocX in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its LayerOne DocX operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect LayerOne DocX

Create your workspace
Sign up free. Nothing to install.
Connect LayerOne DocX once
Add your LayerOne DocX connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.