Integration

doqs.dev integration

doqs.dev fills PDF templates with JSON data and renders HTML into PDF documents. List the PDF templates of the account, fill one with a key-value data object (text, checkbox, date and image fields) and get the filled PDF back as a file, render an HTML page with optional header, footer, page format and margins into a PDF, and list past render submissions. Templates are uploaded and their fields placed in the doqs.dev dashboard. Authentication is an API key sent in the x-api-key header; a development key adds a watermark to filled PDFs and cannot render HTML.

Connect doqs.dev How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in doqs.dev.Built from the 4 doqs.dev tools below, on the connection you add once.

What you can do with doqs.dev

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.

Fill, 1 operation

fill_templateFill templatePOSTFills a PDF template with the values in data and returns the filled PDF as a stored file. Each key of data is a field name defined in the template, and every field with that name receives the value.

Render, 1 operation

render_pdfRender pdfPOSTRenders an HTML document into a PDF with a Chromium engine and returns the PDF as a stored file.

Submission, 1 operation

list_submissionsList submissionsGETLists past HTML-to-PDF render submissions of the account with their id, creation time and outcome (success, error or timeout). Useful to audit renders or find failed ones.

Template, 1 operation

list_templatesList templatesGETLists the PDF templates of the account with their id, name, page count, file size and creation time. Pass a template id to fill_template to produce a filled PDF.

Use doqs.dev from Claude Code, Cursor or Codex

Connect doqs.dev in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its doqs.dev 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 doqs.dev

Create your workspace
Sign up free. Nothing to install.
Connect doqs.dev once
Add your doqs.dev 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.