Integration

Qwilr integration

Qwilr builds interactive web proposals and quotes that buyers view, accept and pay online. Create pages from saved blocks or a template with variable substitutions, list and read pages with their status, links, quote totals and acceptance progress, publish, move, tag or re-block a page, manage quote tax definitions, look up saved blocks and Qwilr Pay gateways, and subscribe to page events (accepted, viewed, set live) by webhook. Accepter names, emails, form answers and audit trail PDFs are left out of page outputs, and the account users route is not exposed because it returns team members' names and emails. Authentication is the account access token from Qwilr API Settings, sent as a bearer token; every call acts on your live account.

Connect Qwilr How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Qwilr.Built from the 13 Qwilr tools below, on the connection you add once.

What you can do with Qwilr

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.

Page, 4 operations

create_pageCreate pagePOSTCreate a Qwilr page from saved blocks (blocks) or from a template (templateId), give exactly one. With published=true the page is public at once and buyers can open its link; leave it false for a draft.
get_pageGet pageGETGet one page with all its fields: status, links (public, editor, PDF), quote and acceptance progress (with expand=acceptance), Qwilr Pay settings and link expiry.
list_pagesList pagesGETList pages, newest first by default, in sets of up to 100. Pass nextCursor back as cursor until it is null. Returns summaries; call get_page for acceptance, quote and payment settings.
update_pageUpdate pagePUTChange a page: publish or unpublish it, set link expiry or Qwilr Pay settings, move it to a folder, add tags, or REPLACE all its content with saved blocks. Only the fields you send change. This edits a real page buyers may see.

Tax, 4 operations

create_taxCreate taxPOSTCreate a quote tax definition (name and rate in percent). Qwilr generates the id unless you give one; the id can never be changed afterwards. Keep the returned id to refer to the tax.
delete_taxDelete taxDELETEDelete a quote tax definition from your account. Nothing restores it: to use it again, create it anew with create_tax.
list_taxesList taxesGETList the quote tax definitions in your account, each with id, name and rate (percent). Use the ids in a quote block's quoteSettings.taxIds.
update_taxUpdate taxPATCHChange a tax definition's name, rate or both (send at least one); fields you leave out are kept. The id cannot be changed: to use another id, delete the tax and create a new one.

Webhook, 3 operations

create_webhookCreate webhookPOSTSubscribe a URL to one Qwilr page event; Qwilr then POSTs every such event to it. Keep the returned id to cancel with delete_webhook. Qwilr documents no delivery signature, so deliveries cannot be verified.
delete_webhookDelete webhookDELETECancel a webhook subscription; Qwilr stops posting its events.
list_webhooksList webhooksGETList the webhook subscriptions created with create_webhook: id, event and target url.

Payment gateway, 1 operation

list_payment_gatewaysList payment gatewaysGETList the Qwilr Pay payment gateways in your account (id and name only). Pass a gateway id as paymentSettings.gatewayId in update_page.

Saved block, 1 operation

list_saved_blocksList saved blocksGETList the saved blocks in your account with their id, name and type. Use a block id in the blocks of create_page or update_page.

Use Qwilr from Claude Code, Cursor or Codex

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

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