Joltly's new MCP plugs your AP and revenue data into Claude Cowork, Codex, or any agentic system β pull invoices, aging reports, and revenue visualizations from a single prompt.
Most of the time you spend in accounting software isn’t spent making decisions — it’s spent getting to the data. Export a CSV, upload it somewhere, build the report, repeat next week. We think that loop is on its way out.
That’s why we built the Joltly MCP — a connector that plugs Joltly directly into Claude Cowork, Codex, or any agentic system you’re already using. Once connected, your agent can pull your invoices, revenue statements, vendor activity, and aging data on demand, and turn any of it into a report or visualization from a single prompt.
Instead of exporting, uploading, and rebuilding reports, you just ask — and the data comes to you.
Under the hood, an MCP is simple: it’s our API with a wrapper that agents know how to speak. Everything documented in the Joltly API docs is exposed through it — any data in your account, your agent can reach.
You ask in plain English — “give me an overview of my invoices” — and the agent does the pulling, flagging, and reporting.
A wrapper around the Joltly API that gives agents structured, secure access to your account — authenticated with your API key.
Your invoices, revenue statements, vendors, and payment data — already coded and reconciled, ready to query.
The whole thing takes a few minutes inside Cowork. And if you hit a snag, just ask your agent to walk you through it — that’s what it’s there for.
Choose “Add custom connector” and name it Joltly.
Use the API URL from our documentation. This is what Cowork uses to reach your account’s data and functionality.
In Joltly, go to Settings → API Keys, copy your key, and enter it when Cowork asks.
Open a new task and try: “Connect to Joltly and give me an overview of my invoices.”
Joltly has already coded and organized your data — so once the agent can reach it, the console becomes the fastest way to work. We’ve been testing this internally, and it’s changed how we use our own product.
Pull your invoices, revenue statements, and expense data into one view — who your purchasers are, what’s coming in, what’s going out.
The agent surfaces failed payments, vendors that need to be paid, and aging-report issues without you hunting for them.
Ask for a revenue visualization and it builds one straight from your Joltly data — no exporting to a spreadsheet first.
Everything Joltly has read and reconciled from your statements is queryable — the agent works from the same source of truth you do.
This is intentional. Reading and reporting on your data is safe to hand to an agent. Payments are different.
We think this is where software is heading generally: the console as the primary interface, with your system of record doing the heavy lifting underneath. This is going to be a game changer for how a lot of our customers interact with their data.
Grab your API key, add the connector, and start asking. And if you’d rather walk through it live, we’re happy to jump on a call and set it up with you.
Get quick answers to common queries in our FAQs.


You only pay for what you use β no seat fees and no modules you don't need. Pricing is a monthly platform fee plus usage on documents processed, ACH payments, mailed checks, and the workflows you turn on. We size it to your actual monthly close so it scales with the work, not your headcount.
A smaller operator running 25 documents, 10 ACH payments, and 2 mailed checks a month would be priced on that exact volume. A larger operator at 100 documents, 50 ACH payments, and 10 checks pays predictably more. You always know what you're spending because it tracks the actual close.
Joltly connects directly to QuickBooks and Quorum On-Demand Accounting, and supports file-based export workflows for systems like PakEnergy and Integra. It manages accounts, items, vendors, partner mappings, JIB clearing, revenue liabilities, and netting accounts inside your existing setup.
Both sides of settlement. On expenses: invoice review, GL coding, approvals, JIB creation, ACH and check payments. On revenue: statement OCR, partner distributions, remittance emails, and netting between JIB receivables and revenue payouts β so your team replaces spreadsheet work and email follow-up during close.
Yes. Your wells, partners, revenue interests, GL mappings, approval flow, export formats, and partner-facing statements are configured per operator. Most customers go live on their existing chart of accounts and ERP setup β no rebuild required.
Faster than most teams expect. Your AP workflow can be live in less than a week β and you don't need to change your current accounting system. Revenue typically takes about two weeks. The only thing we need from you is a sample revenue statement so we can train the AI on your format.
We set up a Microsoft Teams channel or email channel for your team β whichever you prefer. You'll also get the founders' phone numbers for text messaging when you need a fast answer.