Connect LetSign to Cursor and the agent in your editor drafts the proposal, the pricing options and the contract from the brief already sitting in your project - then stages it for your review. Your client opens one link, picks a plan, signs and pays into your own Stripe.
Cursor does the thinking, LetSign does the contracting, Stripe does the collecting. You stay in the loop exactly once - at send time.
No SDK, no webhooks, no integration project. The whole setup is one small JSON file, one connection and one prompt.
Create a .cursor/mcp.json file in your project (or ~/.cursor/mcp.json to make LetSign available in every project) and add an entry with a "url" pointing at the LetSign remote MCP endpoint, with "type" set to "streamableHttp":
{
"mcpServers": {
"letsign": {
"type": "streamableHttp",
"url": "YOUR_LETSIGN_MCP_URL"
}
}
}Grab your LetSign MCP URL from app.letsign.ai, save the file, and Cursor loads the LetSign tools straight into its agent. No extension and no plugin, just that one small file.
In the LetSign app, connect your own Stripe account once. From then on every payment - one-off, subscription, or save-card-on-file - is collected through your Stripe and lands in your account. LetSign never holds your money.
You already keep the client brief in the repo. Ask Cursor's agent to work from it, right in the editor, the way you would brief a colleague. One proven opener:
"Read the client brief in this project and draft the proposal for Halewood Studio from it - three tiers, the middle one at the number in the brief - then stage it in LetSign for my review."
Cursor stages the proposal; nothing sends itself. You read it, tweak anything you like (a discount, net-60 terms, a different tier), and press send. The human send-gate is a feature, not a limitation.
Your client opens one public link, chooses between the plans you offered (conditional pricing built in), verifies their email, signs a binding e-signature and pays through your Stripe - in a single sitting. Remember: the sender never signs. The client does.
Prefer the terminal to an editor pane? The same stack runs in Claude Code. Editing somewhere else? There are playbooks for Windsurf and VS Code + Copilot too.
Cursor drafts the whole proposal with up to several plans your client can choose from - three tiers, optional add-ons, the works - straight from the brief in your repo.
"Has Halewood signed yet?" Cursor checks proposal status through the MCP: opened, plan picked, signed, paid - without you opening a dashboard.
Client asks for net-60 or a 10% discount? Tell Cursor, and it updates the terms and restages the proposal for your review.
One-off invoices, subscriptions, or save-card-on-file - collected through your own Stripe account at signature time, not weeks later.
And everything Cursor does here, you can also do by hand. Every proposal, template and setting is fully editable in the LetSign app - full parity with the MCP. That two-way door is the essence of an agent-native contract: your agent and you work on the same object, and neither is a second-class citizen.
Create a .cursor/mcp.json file in your project, or ~/.cursor/mcp.json to make it available in every project, and add a server entry with a "url" pointing at the remote endpoint and "type" set to "streamableHttp". Save the file and Cursor loads the server's tools straight into its agent. That one small JSON file is all LetSign needs.
No. The setup is a few lines of JSON you paste once into mcp.json, not a programming project. You connect Stripe once inside LetSign, then everything else happens in plain conversation with Cursor's agent. And if you ever prefer to work by hand, every proposal and template is fully editable in the LetSign app.
The Free plan is $0 with a 0.20% fee on payments collected through it. The launch plan is $19 per month until October 1, 2026, and that price is locked until October 1, 2028; after launch the standard price is $49 per month. Paid plans pay 0% on payments up to $20,000 per month, then 0.05% above that.
You do. Cursor drafts and stages the proposal, but nothing sends itself: a human reviews and presses send. And the sender never signs. Your client opens the link, picks a plan, verifies their email, signs a binding e-signature and pays through your Stripe.
Add the mcp.json entry, connect Stripe, and let Cursor stage the next proposal for your review.
START LETSIGN FREE