'%20/%3e%3c/svg%3e){kind=small}
Connect any AI assistant to your finance stack
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to tools and data. Payouts.com is MCP-native: it exposes its large tool library to assistants like Claude, discovers tools dynamically, and renders rich interactive UI widgets right inside the AI chat.
0
tool calls
routed today
routed today
MCP
What the MCP integration provides
Connect an MCP-compatible assistant and the platform's large tool library becomes available to it — discovered dynamically, rendered as rich interactive widgets, and scoped per portal.
Dynamic tool discovery
Assistants find the right tool from the platform's large library at runtime — so new platform capabilities become available to connected assistants without bespoke integration work.
Tool discoveryDiscovering
MCP
0 tools
payouts.createamount, destready
recipients.listlimitready
balance.getcurrencyready
refunds.createpayout_idready
transfers.sendto, amountready
Tools discovered1,840
Rich interactive UI widgets
Tool results render as interactive widgets inside AI chats, not just walls of text — so results show up as usable interfaces in the conversation rather than plain output.
Portal MCP surfaces
Separate MCP surfaces for vendor, client, and employee tooling, so each portal's AI assistant gets the right scope. Tool calls blocked by safety policy are recorded in a dedicated audit view.
Portal MCP surfacesRouting
Portal calls routed86,400
Tools
Every tool an assistant can call
Each capability the platform exposes over MCP maps to a real operation. Browse the full surface here — assistants discover these tools dynamically at runtime, then call them on your behalf.
Connect
Point any assistant at your finance stack.
Connect an MCP-compatible assistant once, and every tool the platform exposes is available to it — discovered dynamically, scoped to what it's allowed to do.
Connect Claude or Cursor
Connect an MCP-compatible assistant — Claude, Cursor, or your own — to the platform's MCP surface at
mcp.payouts.com. Once connected, the assistant discovers and calls the platform's large tool library on your behalf.
Connector handshakeConnecting
initialize…
capabilities…
tools/list…
Assistants connected3,120
Dynamic tool discovery
Assistants find the right tool from the platform's large library at runtime, and tool results stream back as rich interactive widgets rendered right inside the AI chat — not just walls of text.
Tool graphFiltering
—
payouts.create
payouts.list
payouts.cancel
recipients.get
balance.get
refunds.create
transfers.send
payouts.retry
Tool calls today92,400
Portal MCP & blocked-calls audit
Vendor, client, and employee portals each have their own MCP surface scoped to their tools. Tool calls blocked by safety policy are recorded in a dedicated
blocked-MCP-calls audit view, so you can see what an assistant attempted and what was prevented.
Policy gatewayChecking
recipients.get···
payouts.list···
payouts.create · $50k···
balance.get···
blocked-MCP-calls
×payouts.create · $50kover policy
Calls audited312,000
Platform
How MCP fits the rest of the platform
An assistant connected over MCP still operates under scoped, revocable access, and any action that moves money still passes through the three-gate approval, authorization, and execution lifecycle. Tool calls that safety policy blocks are recorded in a dedicated audit view — and because tools are discovered dynamically, new platform capabilities become available without bespoke integration work.
Platform status
All systems operational
Uptime99.997%
p50 latency78ms
p99 latency412ms
Requests / sec · last 60s
- REST APIOperational
- DashboardOperational
- MCP serverOperational
- WebhooksOperational
- ACH · RTP · SEPAOperational
FAQ
Frequently asked questions
Everything you need to know about the Model Context Protocol, which assistants can connect, portal MCP surfaces, and how MCP works with the platform's controls.
Still have questions?
What is MCP?
The Model Context Protocol, an open standard for connecting AI assistants to external tools and data sources.
Which assistants can connect?
MCP-compatible assistants, including Claude, can connect to the platform's tools.
Are there different MCP surfaces per portal?
Yes — vendor, client, and employee portals each have their own MCP surface scoped to their tools.
Does connecting an assistant over MCP weaken security?
No. Assistants operate under scoped, revocable access, money movement still passes through the three gates, and blocked tool calls are audited.
Do I have to integrate each new tool manually?
No. Tools are discovered dynamically, so new capabilities become available to connected assistants automatically.
Connect your
first assistant.
Point Claude or any MCP-compatible assistant at your finance stack. Tools are discovered dynamically and results render as rich interactive widgets right inside the chat.