Connect Qwilr to Claude Code

Make Claude draft proposals and build quotes in Qwilr. From the terminal, inside the sessions where you already work.

How do you connect Qwilr to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Qwilr, you add a Qwilr MCP server: a small hosted service that exposes Qwilr's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Qwilr account. No API keys pasted into config files.

claude mcp add --transport http qwilr https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Qwilr once connected?

Read-write Qwilr access lets Claude draft a new proposal from a template, set the quote and pricing blocks at creation, supply client details, and publish it to a shareable link once you approve. The document assembly that used to mean manual setup happens where the proposal already lives.

Draft a new proposal or quote from an existing Qwilr template
Set pricing, quantities, and line items in a quote block when creating the page
Insert client name, scope, and contact details when the page is created
Assemble content blocks and sections from saved blocks to match a deal
Publish a finished proposal to a shareable link after you approve it
Read a proposal by its page id to check its current details

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Qwilr access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Qwilr API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Qwilr changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Qwilr connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Qwilr connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Qwilr account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Qwilr's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Qwilr?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Qwilr account it signs in with. Revoking access is one click in Qwilr.

More on the Qwilr connector

Qwilr connector for claude.ai SignNow + Claude Code SignRequest + Claude Code Proposify + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us