Skip to main content
Loopfour

MCP

Coming soon

Loopfour's MCP server is coming soon.

If you landed here checking whether Loopfour has a Model Context Protocol server: not yet. Loopfour already runs deterministic finance workflows — approval routing, cash application, reconciliation, close checks — triggered today by a schedule, an event, or a person over the API. Native MCP support, so an agent can trigger those same workflows directly as tools, is what's coming. We're not putting a date on it here.

What carries over

MCP changes who calls the workflow. Not what governs it.

An MCP server is a connector: it lets an agent discover and call a tool. It is not, on its own, a control layer. Here is what an MCP-triggered run is designed to keep from the workflow it's calling.

  • Same workflows, new caller

    Accounts payable and approval routing, accounts receivable and cash application, payment reconciliation, revenue recognition, and month-end close — the categories Loopfour already automates. An agent would trigger them; it would not redefine them.

  • Same permissions

    Not every caller can trigger every workflow today, and that stays true for an agent calling one over MCP. No wider access than the same workflow already has over the API.

  • Same approval gates

    A workflow that requires sign-off before money moves keeps requiring it, whether a schedule, a person, or an agent triggered the run.

  • Same audit trail

    What ran, on what data, and who (or what) approved it, lands in the same per-run record every Loopfour workflow already produces.

Available today

The same workflows, over API and webhooks, right now.

None of this waits on MCP. Loopfour's workflow engine already runs across these connectors and more, triggered via API or webhook today:

  • Stripe
  • QuickBooks
  • NetSuite
  • Xero
  • Sage Intacct
  • Plaid
  • Salesforce
  • HubSpot

FAQ

Common questions from finance leaders.

Not yet. Loopfour's workflow engine already runs these operations — across Stripe, QuickBooks, NetSuite, and the other connectors above — via API and webhook triggers today. Native MCP support, so an agent can call those same workflows directly as tools, is coming soon. We don't have a ship date to share.

Still evaluating a workflow? Contact sales and we will map the first automation path with you.

MCP is coming. The engine it will run on is already live.

Every workflow this page describes — approval routing, cash application, reconciliation, close checks — already runs in production today, over the API. Book a demo and we'll walk through it on your stack, then show you exactly where MCP slots in once it ships.

Book a demo