Proposals in Claude

Beta. If you don't see Settings → Integrations in your Proposals account yet, write to support@proposals.co and we'll switch it on for your team.

Connect Proposals to Claude as a custom connector, and you can turn call notes into a proposal in the same conversation where you prepared for the call. Claude asks Proposals to write the draft, relays any questions to you, publishes when you say so, and then drafts the email with the link. Proposals never sends that email: you do.

What you need

• A Proposals account with integrations switched on.
• A Claude plan that supports custom connectors (remote MCP servers). On team and enterprise plans, an owner or admin usually adds the connector for the organization first, and members then connect their own accounts.
• The server address: https://api.proposals.co/mcp

Connect

Claude's menus change from time to time, so the names below may differ slightly in your account.

1. In Claude, open Settings → Connectors (on team plans, an admin does this in the organization settings).
2. Add a custom connector. Name it Proposals and paste https://api.proposals.co/mcp as the URL. You don't need to fill in any OAuth client details: Proposals registers Claude automatically.
3. Click Connect. Claude opens a Proposals page. Log in if needed and check what the connector is asking for:
   • reading your brands and proposals,
   • creating and changing proposals,
   • publishing proposals, which is unticked by default. Leave it unticked if you'd rather publish in the panel yourself.
4. Approve. You're back in Claude and the connector shows as connected.

In a conversation, make sure the Proposals connector is enabled in the tools menu, then ask. Claude may ask you to allow each tool the first time it uses it; allowing publishing "once" rather than "always" is a sensible default.

Make your first proposal

Here's the transcript of my call with Lila Flowers. Make a proposal: website redesign, 6 pages, $9,000, half upfront and half on delivery. The contact is Anna Novak, anna@lila-flowers.example.

(transcript)

What happens next:

1. Claude creates the proposal. The draft takes 30 to 120 seconds to write; Claude checks back on its own.
2. If the transcript is ambiguous, for example it names two different companies, Claude asks you which one is right instead of guessing.
3. When the draft is ready, you get a summary: client, scope in a few points, price, anything the pre-publish check flagged, and a link to review it in the panel.
4. Ask for changes: "Mention the 5-week timeline and drop the SEO audit."
5. Say "Publish it" to get the public link (only with the publish permission and with no blockers).
6. Ask Claude to write the email. It uses the link exactly as returned and the facts from the proposal. Send it yourself, then tell Claude so the proposal is marked as sent.

Later, "Did Anna open the proposal?" gets you the current status.

Tools the connector adds

Proposals enforces the important rules on its side: without the publish permission, or with a blocker in the pre-publish check, publishing is refused no matter what the model asks for. A price you give is the price on the proposal, and Proposals never makes one up.

Edit a proposal with your own context (Claude Code)

revise_proposal asks Proposals to rewrite the draft. With get_proposal_content and edit_proposal_content, Claude edits it itself, section by section, the way the editing assistant in the builder does, using whatever it has in front of it: the conversation, your files, your notes. In Claude Code, add the server once and log in when Claude Code asks:

claude mcp add --transport http proposals https://api.proposals.co/mcp

Then run /mcp, choose proposals and authenticate; the same Proposals consent page opens in your browser.

Open the proposal for Lila Flowers. Rewrite the scope from notes/lila-scope.md, add an FAQ about hosting after the scope, move the timeline above the price and switch to the editorial theme.

Every edit is saved as a new draft revision and the previous one stays in the version history, so you can undo it with restore_proposal_version. If the draft changed in the panel in the meantime, the edit is refused instead of overwriting it, and Claude reads it again. The client sees the changes only after you publish them.

Good to know

• Every proposal made in Claude is in your panel, marked "Created in Claude", and you can keep editing it there.
• The connection acts on your behalf and never has more rights than your Proposals account.
• Limits and plan usage are the same as for API keys. See Limits.

Disconnect

In Proposals, go to Settings → Integrations → Connected apps and disconnect Claude. Access ends immediately. You can also remove the connector in Claude's settings.

Troubleshooting