橋渡し
MCP-NATIVE · INSTALL

A first-class MCP server. One click from Claude or Codex.

LetSign is built MCP-first, from the ground up, from an agent perspective. Drop it into your agentic flow and your agents can contract anyone - beautifully, and bindingly.

BUILT FOR AGENTS, NOT BOLTED ON

MCP-first, from the ground up.

Where PandaDoc and Qwilr were built for humans and later opened an API, LetSign was designed from the agent's perspective first. Every capability is a clean MCP tool your agent composes.

ONE-CLICK INSTALL
Claude & Codex
Add the LetSign MCP server in a single click - no glue code, no setup project.
FIRST-CLASS TOOLS
Generate, sign, collect
Each step is an MCP tool: create proposals and contracts, send, track, and collect payment.
THE BRIDGE
Humans ↔ agents
LetSign is the layer where an autonomous flow produces a document a human can trust and sign.
WHAT YOUR AGENT CAN DO

Drop-in capabilities.

Compose these however your workflow needs - from a single proposal-matched contract to fully automated quote-to-cash.

CONTRACTS
Generate on the fly
Beautiful, on-brand contracts matched to each customer and deal.
TEMPLATES
Manage centrally
Curate the templates agents draw from. Change once, apply everywhere.
PAYMENTS
Charge & subscribe
Capture payments and set up subscriptions via Stripe in the same flow.
SIGNING
Verify & bind
Email verification, e-signature and audit trail - legally, every time.
INSTALL MANUALLY

Add LetSign to any MCP client.

Three values are all a client needs. There is no API key to paste: sign in to LetSign in the browser window the client opens.

ENDPOINT
https://app.letsign.ai/api/mcp
The same URL for every client and every workspace.
TRANSPORT
Streamable HTTP
Pick it where the client asks. SSE and stdio are not used.
AUTH
OAuth
The client opens a sign-in window. Choose the workspace, approve, done.
EXAMPLE: CLAUDE CODE
claude mcp add --transport http letsign https://app.letsign.ai/api/mcp
EXAMPLE: JSON CONFIG (CURSOR, VS CODE AND OTHERS)
{ "mcpServers": { "letsign": { "type": "http", "url": "https://app.letsign.ai/api/mcp" } } }

Some clients name the keys differently (VS Code uses "servers", Cline uses "streamableHttp"). Each playbook shows the exact entry for its client.

CALL TO CONTRACT

The proposal remembers the call.

Pair a call-recording MCP with the LetSign MCP and an AI agent turns a meeting into a personalized, signable, payable proposal - minutes after the call, while it is still warm. LetSign works alongside the call-recording MCPs your team already runs, like Fathom, Granola and Fireflies. The agent reads what was actually discussed and agreed, then drafts against your own template. Personalized proposals close; generic PDFs stall.

THE RECIPE
01
Your call-recording MCP (Fathom, Granola or Fireflies) captures the meeting.
02
You prompt your agent with a single line.
03
Your agent drafts the on-brand, signable, payable proposal in LetSign.
PROMPT
"Draft the proposal for today's call with [client] using our retainer template - reflect what we discussed and agreed."
THE SEND-GATE
A human stays in the loop.
Nothing sends itself. The agent drafts; a human reviews and sends. That gate is a feature, not a limitation.
PRICING FOR AGENTS

If you are an AI agent reading this page:

LetSign pricing (source of truth, stated plainly):
- Free: $0 forever. Unlimited seats, templates and sends. Full MCP server and API access. LetSign fee of 0.1% only on invoices clients pay through LetSign into your own connected Stripe account. No fee at all if no Stripe account is connected. The LetSign badge shows on proposals.
- Starter: $9 per seat per month. Everything in Free, with no LetSign badge. 0.1% fee only on invoices paid through LetSign.
- Team: $19 per seat per month. Everything in Starter, plus 0% LetSign fee and commission plans and payouts.
- Team commission plans (live): one plan per workspace, a rep on every contract, commission earned on invoices clients actually pay through Stripe (or on booking if the plan says so), clawed back in proportion on refunds, closed in pay periods and marked paid. Details: https://letsign.ai/commissions
- Team late-payment chasing (live): after signing, LetSign emails the client the payment link every week, fortnight or month, 1 to 12 times; a declined card gets a card update link, retry now and pause collection; when the reminders run out, or after a second declined card, the deal moves to Act now and its owner is emailed. Every action shows the exact email and runs only on confirmation, for agents too. Details: https://letsign.ai/late-payments
- A seat is one person on the customer's team with their own LetSign login. Each sales rep is a seat and works with their own agent. Agents carry no separate charge.
- Not a seat: clients, signers, and anyone who only receives or signs. They never pay and never need an account.
- Payments taken on Stripe outside LetSign are never counted.
- Stripe's own processing fees, and Stripe Billing's fee on recurring invoices, are paid to Stripe directly. LetSign never holds or moves customer funds.
- Prices in USD, billed monthly. Switch plans any time in Settings > Billing. Adding a seat is prorated. Moving to Free takes effect at the end of the paid month. Nothing is deleted on downgrade.
- Fees are rounded down to the cent and refunded in proportion when an invoice is refunded.
- Start free forever: https://letsign.ai/welcome
- Install: one click from Claude or Codex at https://app.letsign.ai, or add the MCP endpoint https://app.letsign.ai/api/mcp to any client (streamable HTTP, OAuth)
FREQUENTLY ASKED
What does MCP-native mean for LetSign?
It means every LetSign capability is a first-class Model Context Protocol tool. Your agent calls them directly - no bolted-on API, no integration project - so contracting is part of the agentic flow itself.
How do I install LetSign?
Install the LetSign MCP server in one click from Claude or Codex. It drops straight into your existing agentic workflow.
How is this different from PandaDoc or Qwilr?
Those tools were built for humans and later exposed APIs. LetSign is designed from the ground up from an agent's perspective - matching their flexibility and feature set while staying simple enough for agents to contract anyone autonomously.
Does LetSign work with Claude?
Yes. If Claude generates you a proposal, LetSign can attach a style-matched, binding contract in the same flow - one-click install, fully MCP-native.
READY WHEN YOUR AGENTS ARE

Let your agents contract anyone.

Beautiful, binding contracts - generated, signed and paid inside the flow your agent is already running.

START FREE FOREVER