Add LetSign as an MCP server in your openclaw.json and your self-hosted OpenClaw agent can draft the proposal, the pricing options and the contract - then stage it for your review. Your client opens one link, picks a plan, signs a binding e-signature and pays into your own Stripe.
OpenClaw does the drafting on your own hardware, LetSign does the contracting, Stripe does the collecting. You stay in the loop exactly once - at send time. LetSign is the agent-native layer that actually closes the deal your OpenClaw agent started.
No SDK, no webhooks, no integration project. The whole setup is one mcpServers entry, one Stripe connection and one instruction to your agent.
OpenClaw has first-class Model Context Protocol (MCP) support with full stdio and HTTP/SSE transports. Add an mcpServers entry to openclaw.json pointing at the LetSign MCP endpoint (you get it from app.letsign.ai). OpenClaw's built-in OAuth handles auth for servers that need it, so on restart your self-hosted agent loads LetSign's tools automatically - no custom code, no community package.
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.
OpenClaw is driven through messaging apps like Telegram or WhatsApp, and it remembers context across sessions - so one message is enough. A proven instruction:
"Draft a LetSign proposal for Meridian Studio - three tiers, the middle one at $4k/mo - from the scope we discussed, and stage it for my review."
The agent drafts and stages the proposal through the LetSign MCP; nothing sends itself. You read it in LetSign, 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. Because OpenClaw runs on a schedule with persistent memory, it can log the win and notify you afterwards. Remember: the sender never signs. The client does.
Prefer a conversational assistant to a self-hosted agent? The same LetSign MCP drops into Claude, Codex and Cursor. See the full AI sales automation tools map for every host.
Your OpenClaw agent drafts the whole proposal with up to several plans your client can choose from - three tiers, optional add-ons, the works - straight from the scope you gave it.
"Has Meridian signed yet?" Message your agent and it reads proposal state through the MCP: opened, plan picked, signed, paid - all without you opening a dashboard.
Client asks for net-60 or a 10% discount? One more message 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 your agent 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. OpenClaw has first-class Model Context Protocol (MCP) support with full stdio and HTTP/SSE transports. You add an mcpServers block to openclaw.json and point it at any MCP server; the self-hosted agent gains those tools. LetSign is an MCP server, so it drops straight into that mcpServers config.
No. You add one mcpServers entry to openclaw.json pointing at the LetSign MCP endpoint (stdio or HTTP/SSE), and OpenClaw's built-in OAuth handles authentication for servers that need it. You connect Stripe once inside LetSign, then your agent does the drafting. Every proposal and template is also fully editable by hand 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. Your OpenClaw agent drafts and stages the proposal, but nothing sends itself: a human reviews and presses send. And the sender never signs. Your client opens the public link, picks a plan, verifies their email, signs a binding e-signature and pays through your Stripe.
Add the mcpServers entry, connect Stripe, and let your OpenClaw agent stage the next proposal for your review.
START LETSIGN FREE