MCP
Wrenbase runs a live MCP server, so you can drive your invoicing from an AI assistant. Connect a client, and you can create and send invoices, pull a daily brief, and chase overdue payments in plain language.
Why it’s useful
The Model Context Protocol is the standard for giving AI assistants a set of tools they can call. Wrenbase exposes its own tools over MCP, so instead of clicking through the dashboard you can just say what you want: “send the invoice to Acme,” “what needs my attention today,” “mark INV-042 paid.”
- It’s live. Connect a client and start using it today. This isn’t a preview.
- Works with any MCP client. One remote URL and a key, no local install.
- Real work, not read-only. Create and send invoices, generate payment links, mark invoices paid, and get a triage brief, all from chat.
- Safe by default. Everything runs as you, with your limits, and every change is written to your audit trail. Moving money still happens in the app, never straight from a tool call.
In this section
Start here
Get your key
Create an API key from the Developer area and link it to you or an agent.
Connect
Connect a client
Point any MCP-capable client at your Wrenbase server URL and key.
Reference
Tools
The tools Wrenbase exposes over MCP, grouped by what they do.
Trust
Security
How keys, permissions, revocation, and the audit trail keep it safe.
MCP is available on the higher plans. See wrenbase.com/pricing for what’s included where.
Frequently asked questions
- What can I do with Wrenbase's MCP server?
- Wrenbase runs a live MCP server, so you can drive your invoicing from an AI assistant. Connect a client and you can create and send invoices, generate payment links, mark invoices paid, and pull a daily brief, all in plain language.
- Do I need to install anything to use Wrenbase over MCP?
- No. It works with any MCP client using one remote URL and a key, with no local install.
- Is Wrenbase MCP safe to use?
- Yes. Everything runs as you, with your limits, and every change is written to your audit trail. Moving money still happens in the app, never straight from a tool call.