The dashboard and the MCP server hit the same non-custodial backend. Pick the operator, not a second product.
Dashboard
Humans. Invoice wizard, branding, PDF preview, payment list, webhook settings, CSV export. Finance at month-end. First-time setup. Demos.
If you send a handful of invoices a month, stop here.
MCP
Agents and IDEs. Typed tools: create invoice, list invoices, get status, void. Cursor / Claude Desktop / a custom agent. No browser context.
Good for: “create a USDC invoice for Acme, $12,000, due in 14 days.” Ops agents polling unpaid. Support asking “has 1042 been paid?”
MCP is not a webhook. Production “paid” still comes from signed delivery after on-chain confirmation.
Split that actually works
- Branding, templates, webhook secrets: dashboard once.
- High-volume create / status: MCP.
- Reconciliation and disputes: dashboard (you need the tx detail page).
Both settle to addresses bound at issuance. The platform does not hold a key that can move the payment.
Longer write-up: MCP vs dashboard workflows.
I work on this at Settlematic. Collect is live. Gateway is sandbox.
Top comments (0)