Connect LetSign to Cline and your VS Code agent drafts the proposal, the pricing options and the contract without leaving the editor - then stages it for your review. Your client opens one link, picks a plan, signs and pays into your own Stripe.
Cline 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 two connections and one prompt.
In VS Code, open Cline's MCP settings and switch to the "Remote Servers" tab: enter a name and paste the LetSign remote MCP URL from app.letsign.ai. Prefer editing config directly? Add the same server to cline_mcp_settings.json with "type": "streamableHttp" and the server "url". One honest note: remote HTTP servers are a newer path in Cline than local stdio ones, so keep the extension up to date and check the server's status in the MCP settings screen if a connection misbehaves.
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.
Cline already sits next to your project files and notes, so brief it like a teammate:
"We just wrapped the Meridian Consulting build. Draft the maintenance retainer proposal from the scope notes in this repo - three tiers, the middle one at the number in the notes - and stage it for my review."
Cline 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.
Running GitHub Copilot in the same editor? The same stack works in the VS Code + Copilot playbook. On Cursor instead? Covered too. And if you live in the terminal, Claude Code runs the same play.
Cline drafts the whole proposal with up to several plans your client can choose from - three tiers, optional add-ons, the works - straight from the notes and context in your workspace.
"Has Meridian signed yet?" Cline checks proposal status through the MCP: opened, plan picked, signed, paid - without you leaving the editor.
Client asks for net-60 or a 10% discount? Tell Cline, 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 Cline 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.
Yes. Cline supports remote MCP servers over streamable HTTP. In VS Code, open Cline's MCP settings and use the Remote Servers tab: give the server a name and paste its URL. The same entry can also live in cline_mcp_settings.json with type streamableHttp and the server URL. Remote HTTP support is newer in Cline than the local stdio path, so keep the extension updated and re-open the MCP settings screen if a connection ever drops.
No. The Remote Servers tab is a form with two fields, a name and a URL; the JSON file is an optional alternative, not a requirement. You connect Stripe once inside LetSign, then everything else happens in plain conversation with Cline. 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. Cline 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 server, connect Stripe, and let Cline stage the next proposal for your review.
START LETSIGN FREE