Let Claudesend your invoices.

MCP (Model Context Protocol) is the standard for connecting AI agents to real tools and data. When you connect Holdings to Claude, ChatGPT, or Cursor, your AI can actually draft invoices, take payments, and see when clients paid — instead of just talking about it.

Any AI that supports MCP or the Holdings API — Claude Desktop, Claude web, ChatGPT (via custom GPT), Cursor, Zed, Windsurf, and any custom agent. If you're using an AI to run your business, it can use Holdings.

Yes. Send unlimited invoices and quotes, take card and bank payments, manage clients — all free forever. No monthly fee. No trial. We make money on payment processing (3% + $0.30 per payment collected), same as any card processor.

3% + $0.30 per payment collected. That's it. No monthly fee, no seat pricing, no per-invoice fee, no per-agent fee. Payments settle to your Holdings account in 1–2 business days.

No. If you're comfortable in Claude, ChatGPT, or Cursor, connecting Holdings takes about 30 seconds — you paste a key or click a connector, and your AI can send invoices immediately. You don't need to understand the protocol.

Yes. The web app and the free invoice generator do exactly the same job. Same product, same free tier — use the interface you want.

The MCP server is in active build. Join the waitlist below to be first when it ships. In the meantime, the invoicing product (web + API) is available today at getholdings.com/invoicing.

Yes. Xero and QuickBooks both charge $30–80/month to send an invoice, and their MCPs are dev-toolable (edit JSON, paste OAuth secrets). Holdings invoicing is free — and the MCP is built for one-click connect from your AI.

Sign up for a free Holdings account, generate an API key in Settings → API Keys, then add Holdings to your Claude Desktop configuration file (claude_desktop_config.json). Paste this MCP server config, add your key, and restart Claude Desktop. That's the whole setup. Once connected, ask Claude anything: 'Draft an invoice for Acme,' 'Follow up on unpaid invoices,' 'What's owed to me?'

Two ways: (1) Custom GPT — search 'Holdings Invoicing' in the GPT Store, click Connect, sign into Holdings once, done. (2) Native MCP connectors (rolling out) — add Holdings as a connector in ChatGPT settings. Both let you tell ChatGPT to draft, send, and track invoices in normal conversation.

Yes. Add Holdings to your MCP server config (~/.cursor/mcp.json or the equivalent for Zed/Windsurf) with your Holdings API key. Then any AI chat in your editor can draft invoices, look up client info, and record payments — right next to your code.

Yes. Two paths: (1) Point your agent at Holdings' REST API and pass Bearer <api_key> — works with anything that can make HTTP calls. (2) Connect to our MCP server over stdio or SSE using your language's MCP SDK. All the invoicing endpoints (create, send, list, mark paid, refund, void) are exposed.

Everything you can do in the Holdings web app: create invoices with line items and taxes; send them by email or generate a shareable payment link; look up client contact info and payment history; check whether a specific invoice is paid; list overdue invoices; draft polite payment follow-ups; convert a quote to an invoice; issue refunds; void mistakes. Your AI has the same permissions your API key grants.

No — by design. By default, AI actions create invoices in draft state. Sending requires an explicit action, and you can configure per-key scopes so, for example, the agent can draft but not send. You always see the drafted invoice before it goes out. This is the same 'human in the loop' pattern MCP was built for.

No. Your clients get a normal invoice email with a payment link. They click, pay by card or bank, and get a receipt. The AI is on your side of the transaction only — it's how you create and manage invoices. Your clients see standard, professional Holdings invoices.

Card (Visa, Mastercard, American Express, Discover, Diners Club, JCB) and ACH bank transfers (US clients). Every invoice includes a hosted payment page with a QR code so clients can pay from mobile, desktop, in-person, or by scanning a printed invoice.

Yes — that's roughly the same rate Stripe, Square, and PayPal charge for card processing. Most invoicing tools (QuickBooks, FreshBooks, Xero) also charge a monthly subscription ($20–80/mo) ON TOP of the processing fee. Holdings drops the monthly fee entirely — you only pay when you actually get paid.

We take 3% + $0.30 out of each payment collected — same as any card processor. If your business is generating revenue through Holdings invoicing, we make a small margin on each transaction. If you're not getting paid, we don't get paid either. It's aligned incentives: our revenue only exists if yours does.

Real examples: 'Invoice Acme Corp for 12 hours at $150.' 'Send Sarah at Northwind a $2,500 invoice for the November retainer.' 'Draft an invoice for last week's design work, three revisions at $850 each.' 'Follow up on any invoices more than 14 days overdue.' 'What's my outstanding balance across all clients?' 'Set up a monthly recurring invoice for XYZ Consulting at $5,000.'

Yes. Ask 'Did Acme pay?' or 'Show me unpaid invoices' and your AI queries Holdings in real time. When you get an update at Monday standup or your accountant asks for A/R aging, the numbers are pulled from live data, not stale spreadsheets.

Yes. Tell your AI 'Set up a monthly retainer invoice for Client X at $3,000, due net 15' and it configures the schedule. From then on, invoices generate and send automatically. Great for consultants, agencies, and any retainer business.

Yes. Free plan includes your business name, contact info, and payment terms. Software plan ($25/mo) removes the 'Powered by Holdings' branding and lets you use your own logo, brand colors, and custom email templates. Your AI can adjust invoice fields, notes, and terms per-invoice too.

You can send invoices to international clients today — they receive a professional invoice with a payment link that accepts most major card networks. Full multi-currency support and international ACH are on the roadmap. For now, invoices are denominated in USD and clients pay by international card.

PayPal and Stripe are great for accepting payments, but their invoicing UX is minimal — no client management, no quotes, no automatic payment tracking on their invoice product. Holdings gives you a full invoicing workflow (clients, quotes, recurring, follow-ups, reporting) AND payment processing, at the same or lower cost.

Yes. Give your accountant or bookkeeper their own Holdings login (or share an API key), and they can pull invoicing data, reconcile payments, and produce reports. If they use AI themselves (many do now), Holdings connects into their workflow the same way.

Yes. Holdings is SOC 1 certified. All data in transit is TLS-encrypted. API keys are scoped and revocable per-integration — if you compromise a key, revoke it in one click and generate a new one without touching your other AI setups. Payment processing runs on PCI-compliant infrastructure.

Your Holdings account and data don't care which AI you use. Cancel Cursor, switch from Claude to a new agent — your invoices, clients, and payment history are yours. Just revoke the old API key and issue a new one. Zero lock-in to any AI vendor.

Yes. Two ways: (1) The Claude and ChatGPT mobile apps both support the connector — draft invoices from your phone the same way you would on desktop. (2) The Holdings web app is mobile-responsive if you want to click-through instead. QR-code payment links work great for in-person invoicing on-site.

Holdings tracks all invoicing revenue and produces a year-end summary (paid invoices, refunds, fees) you can hand to your accountant. On the Software plan ($25/mo), full double-entry accounting produces P&L, balance sheet, and 1099-ready contractor payment reports.

Email support@getholdings.com — real humans, typically responding within a few hours during business days. Founders read every support email during launch. Docs and API reference at docs.getholdings.com (rolling out with MCP launch).

The Holdings platform runs on a modern cloud infrastructure with target 99.9% uptime. Formal SLAs are available on request for larger accounts. Payment processing is handled by our card processing partners (same infrastructure as Stripe/Square) — payments continue to process even during any platform maintenance window.