Skip to content
Get started

AI agents (MCP)

Doquill runs a Model Context Protocol server that lets an AI agent author templates in your workspace. The agent writes the template files, schema and sample data, renders previews and looks at the pages as images, then fixes what looks wrong. It publishes only when you ask it to.

The server address is https://mcp.doquill.com/mcp (Streamable HTTP). You can connect in two ways: sign in with your Doquill account, or use an API key.

Use this for Claude Code, Cursor, OpenCode, Claude.ai, Claude Desktop and other clients that support MCP authorization.

  1. Add the server to your client.

    claude mcp add --transport http doquill https://mcp.doquill.com/mcp

    Then run /mcp in Claude Code, pick doquill and choose to authenticate.

  2. Sign in to Doquill in the browser window that opens.

  3. Pick the workspace the app may use and click Allow. Only Team and Business workspaces can be picked.

The app then acts as you in that workspace, with the permissions your role has there. To connect it to another workspace, add the server a second time.

The connection keeps working as long as the app uses it at least once every 30 days. To end it, open Account in the app and click Disconnect under Connected apps. A connection also stops working if you leave the workspace or are removed from it, and being invited back doesn’t restore it.

Use an API key for clients that only support custom headers, or when the agent should have fewer permissions than you do.

  1. In the app, open Developers → API keys and click Create Key. Under Permissions, select:

    Permission Lets the agent
    create_template create new templates
    update_template edit files, schema, sample data, page settings and stylesheets
    render preview templates
    publish_template publish a draft (leave it out to keep publishing to yourself)
    delete_template delete templates (optional)
  2. Add the server to your client, with the key as a bearer token.

    claude mcp add --transport http doquill https://mcp.doquill.com/mcp \
    --header "Authorization: Bearer <api-key>"

    Other clients that support Streamable HTTP and custom headers are set up the same way.

For example: “Create an invoice template in Doquill using Tailwind, with a line-items table and totals. Preview it with a long item list.”

Open the template in the app to review the draft, or tell the agent to publish it.

Tool What it does
list_templates, get_template, list_template_versions Read templates and their published versions
create_template Create a blank template
write_template_files, edit_template_file Write whole files or change part of a file
update_template_data Set the JSON Schema and sample data
update_template_settings Rename the template and set page size, margins and height
list_assets, set_template_css List images and stylesheets, and turn stylesheets (including Tailwind) on or off for a template
preview_template Render the draft or a published version and return page images, with the sample data or data the agent passes
publish_template Publish the draft as a new version
delete_template Delete a template
get_authoring_guide Read the template language and function reference

The agent edits only the draft. API renders keep using the latest published version until the draft is published.

The agent can’t upload assets. Upload images and stylesheets in the app first, and tell the agent which ones to use.

Previews made through MCP have their own rate limit, separate from your render quota: 30 per minute on Team and 60 on Business. Each preview returns up to 10 pages.