Connect Proposify to Claude Code

Make Claude build proposals from templates in Proposify. From the terminal, inside the sessions where you already work.

How do you connect Proposify to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Proposify, you add a Proposify MCP server: a small hosted service that exposes Proposify'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 Proposify account. No API keys pasted into config files.

claude mcp add --transport http proposify 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 Proposify once connected?

Full read-write Proposify access lets Claude create a proposal from a template, set its document fields and totals, add predefined sections and custom fields, and associate the right client. The draft prep that used to mean clicking through the Proposify editor happens where the request already started.

Create a proposal from a template and populate its document fields
Set document-level totals and amounts on a quote or proposal
Associate an existing client or company with a proposal
Add predefined sections to a draft proposal
Set or update custom fields on a proposal
Update a draft proposal's content or fields before it goes out

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 Proposify 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 Proposify API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Proposify 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 Proposify 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 Proposify 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 Proposify 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 Proposify'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 Proposify?

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 Proposify account it signs in with. Revoking access is one click in Proposify.

More on the Proposify connector

Proposify connector for claude.ai SignNow + Claude Code SignRequest + Claude Code Qwilr + 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