TrueLayer MCP for AI. Automate Payments, Payouts, and Account Reconciliation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
TrueLayer manages open banking payments, payouts, and mandated billing cycles directly through your AI client. Your agent can check account balances (`get_data_account_balance`), list bank transactions, create instant bank transfers (`create_payment`), process refunds, or set up recurring mandates—all from a conversation.
What AI agents can do with TrueLayer Automation
Create mandate
Sets up a Variable Recurring Payment (VRP) mandate.
Create payment
Creates a new single payment, requiring amount, currency, method, and beneficiary details.
Create payout
Handles the creation of a new payout (either open or closed loop).
Create and manage Variable Recurring Payment (VRP) mandates for automated billing cycles.
Initiate single bank payments using required details like amount, currency, beneficiary, and payment method.
Create new payouts, supporting both closed-loop (internal) or open-loop (external) transfers.
Generate a refund for a previous payment, ensuring the amount does not exceed the original transaction value.
Retrieve real-time balance details for specific data accounts linked to the user.
Fetch detailed transaction histories for both merchant and data accounts.
Ask an AI about this
Waiting for input…
What AI agents can do with TrueLayer: 13 Tools for Financial Operations
These tools allow your agent to perform every financial operation required in open banking—from checking account status to executing complex transfers.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using TrueLayer on VinkiusCreate Mandate
Sets up a Variable Recurring Payment (VRP) mandate.
Create Payment
Creates a new single payment, requiring amount, currency, method, and beneficiary...
Create Payout
Handles the creation of a new payout (either open or closed loop).
Create Refund
Processes a refund for an existing payment, ensuring it stays under the original...
Get Data Account Balance
Retrieves the current balance for a specific data account.
Get Merchant Account
Fetches detailed information and status for a specified merchant account.
List Data Account Transactions
Lists all transaction records associated with a user's data account.
List Data Accounts
Retrieves a list of the user's connected bank accounts (requires consent token).
List Merchant Account Transactions
Lists all transaction records for a specific merchant account.
List Merchant Accounts
Retrieves a list of all TrueLayer-managed merchant accounts belonging to the user.
List Payment Sources
Lists available payment sources tied to a specific merchant account.
List Providers
Retrieves a list of all supported banking providers in various regions.
Verify Account
Confirms ownership and details for a specified bank account.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The TrueLayer integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with TrueLayer, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by TrueLayer. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 13 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The old way of managing payouts means jumping between systems, logging in multiple times, and cross-referencing spreadsheets to confirm every single transaction., Solved with Vinkius AI Gateway
Today, if you need to reconcile a month's worth of disbursements, you typically have to export data from the primary banking dashboard, manually download settlement reports from the payout system, and then cross-reference those two massive CSV files in Excel. It’s slow, it’s tedious, and frankly, someone always misses a row.
With this MCP server, your agent pulls all that data instantly. You ask for transaction history on multiple accounts (`list_merchant_account_transactions`), and the results stream back structured and ready to use. You get an immediate, unified view of every penny moving.
TrueLayer MCP Server: Process payouts, mandates, and refunds with a single conversational command.
Manual payout management involves generating batches in the platform UI, waiting for file generation, and then uploading those files to another system. This entire sequence adds hours of operational overhead just to confirm funds were sent.
Now, you tell your agent exactly what needs to happen. You run `create_payout` or `create_payment`. The tool handles the API handshake, ensuring the transfer goes out correctly and giving instant confirmation. It's done in conversation.
What your AI can actually do with this
Your agent manages TrueLayer payments and payouts using open banking data. You can handle everything from setting up automated billing cycles to initiating instant transfers, all through conversation.
For managing connected bank accounts and real-time financial data, you've got a few tools at your disposal. You can first run list_data_accounts to get a list of all the user's connected banks—you gotta provide that consent token for this one. Once you know what’s available, you use verify_account to confirm ownership and check the details for any specific bank account.
To see where the money is right now, run get_data_account_balance to retrieve the current balance on a data account. You can pull detailed transaction histories using list_data_account_transactions, which lists all records associated with that user's data account.
When it comes to TrueLayer-managed merchant accounts, you have another set of controls. To see what accounts are active under the platform, run list_merchant_accounts to get a list of every TrueLayer-managed account belonging to the user. You can then pull specific details and status information for any one account by calling get_merchant_account.
If you need transaction history for those merchant accounts, use list_merchant_account_transactions to fetch all records there. You'll also find that your agent can look up available payment sources tied to a specific merchant account using list_payment_sources, and if you just wanna know what banks are supported everywhere, you run list_providers to get a list of those regions.
Handling money movement is the core of this server. You'll start by setting up automated billing cycles; running create_mandate establishes a Variable Recurring Payment (VRP) mandate for that purpose. For single transfers, you use create_payment, which needs an amount, currency, method, and beneficiary to make it work. If you need to send money out—whether it's internal or external—you call create_payout to handle the new payout creation.
You can also issue a refund for previous transactions by running create_refund; this tool makes sure the refund amount never exceeds the original payment value.
These tools let you build out complex financial workflows entirely through natural language prompts.
019ea60c-38f9-7105-8453-2ddfb061e28a 
Here's how it actually works
The bottom line is: You move from conversational intent directly into auditable, actionable financial requests without switching screens or writing code.
Subscribe to this server and enter your TrueLayer Access Token.
Your AI agent calls a specific tool, such as get_data_account_balance, passing required identifiers (like an account ID).
The tool executes the request against TrueLayer's API and returns structured data or confirmation status to your client.
Who is this actually for?
Fintech developers building payment gateways need this for testing complex flows without leaving their IDE. Operations managers use it to automate reconciliation and payout processing when they're tired of clicking through dozens of dashboards at 2 a.m. Finance teams rely on it to monitor merchant account health and audit transaction records instantly.
Integrates payment flows, running test mandates (create_mandate) or payments (create_payment) directly from their code editor.
Automates payouts and refunds to vendors. They use the agent to confirm funds are available before executing a create_payout call.
Reconciles daily transactions by listing account balances (get_data_account_balance) and checking merchant transaction history (list_merchant_account_transactions).
What Changes When You Connect
Process funds transfers instantly. Use create_payment or create_payout to execute bank transfers in one step, eliminating the need for multiple API calls for simple transactions.
Audit accounts faster than ever. Running list_merchant_account_transactions gives you full visibility into a merchant's history without navigating web dashboards.
Handle complex billing logic. Use create_mandate to set up Variable Recurring Payments (VRP) and automate subscriptions reliably, year after year.
Maintain data integrity. Before initiating any payment, check the funds first with get_data_account_balance. This prevents failed transactions due to insufficient funds.
Manage all accounts from one place. Listing both merchant accounts (list_merchant_accounts) and user bank accounts (list_data_accounts) gives a complete financial picture.
See it in action
The Quarterly Reconciliation Task
A finance analyst needs to verify payouts for 50 vendors. Instead of logging into the portal and running reports, they ask their agent: 'List all merchant accounts' (list_merchant_accounts), then ask for the transaction history on each one (list_merchant_account_transactions) to confirm recent disbursements. The agent gathers the data in seconds.
Handling a Failed Subscription
A customer's recurring bill failed because their bank account details changed. An operations manager asks the agent to 'Verify this new bank account.' The agent runs verify_account, confirms ownership, and then uses create_mandate to set up the correct VRP mandate.
Closing a Payment Loop
A merchant needs to give a client a refund. Instead of manually calculating amounts, they instruct the agent: 'Refund $75.00 for payment ID XYZ.' The tool runs create_refund, ensuring the amount is valid against the original transaction.
Verifying Operational Status
A developer needs to know if a new payout batch will clear. They first check the overall merchant account status using get_merchant_account and then use list_data_accounts to confirm that the required data sources are connected.
The honest tradeoffs
Assuming funds are available.
The developer just runs 'Create a payment of $10,000' (create_payment) without checking the balance. The system fails hours later with an insufficient funds error, wasting time and API calls.
Always check first. Before calling create_payment, you must call get_data_account_balance to confirm available funds. Only proceed if the returned balance meets or exceeds the required amount.
Mixing up account types.
Confusing a user's personal bank data (Data API) with the merchant's operational ledger (Merchant API). This leads to incorrect fund reporting and failed reconciliation reports.
Know your tools. Use list_data_accounts when dealing with customer-provided banking details, but use list_merchant_accounts for funds tied directly to the business operation.
Manually listing all providers.
Trying to figure out which banks are supported by clicking through documentation. This is slow and error-prone when checking regional availability.
Just ask the agent: 'List available banking providers.' The tool runs list_providers and gives you a clean list of supported regions and institutions.
When It Fits, When It Doesn't
Use this server if your core business logic involves moving money, establishing recurring billing, or auditing account balances. If the process requires checking fund availability before acting (e.g., paying someone), this is essential. Don't use it if you just need to submit a simple web form—those inputs belong in a dedicated application API. You are here for complex financial state changes. Specifically, if you are building an automated payout system, the necessary sequence is: 1. list_merchant_accounts (to find the source). 2. get_data_account_balance (to check funds). 3. create_payout (the action). Never skip step two.
Questions you might have
How do I list all my merchant accounts using TrueLayer MCP Server? +
You run list_merchant_accounts. This tool fetches a complete list of every account linked to your merchant profile, giving you the IDs needed for subsequent actions.
Can I check bank balances with get_data_account_balance? +
Yes. get_data_account_balance retrieves real-time balance data from a user's connected account, allowing you to confirm funds before initiating transfers.
What is the difference between create_payment and create_payout? +
Use create_payment for standard payments initiated within your immediate merchant flow. Use create_payout when sending money out to external parties or managing a broader dispersal of funds.
How do I set up recurring billing with create_mandate? +
create_mandate establishes the Variable Recurring Payment (VRP) mandate. This is the formal step that allows you to automatically bill a customer later without sending repeated API calls.
When should I use the `create_refund` tool to handle payments? +
You use create_refund when a customer needs their money back after a payment. The process requires linking it to an existing transaction, and you can't refund more than the original amount.
How do I check historical activity using `list_data_account_transactions`? +
This tool pulls the full list of transactions from a user’s bank data account. Because this is sensitive data, you'll need to provide the required user consent token for it to work.
What does `verify_account` do before I send any money? +
It confirms that you actually own the bank account you are trying to access. This verification step is a security measure; we won't process payments without confirming ownership first.
How can I find out which banks TrueLayer supports using `list_providers`? +
Running list_providers gives you a complete list of all supported banking providers. Use this to confirm that the financial institutions in your target region are integrated.
Can I issue a refund for a specific payment using this server? +
Yes! Use the create_refund tool by providing the payment_id and the amount_in_minor (e.g., 100 for £1.00). The agent will process the repayment against the original transaction.
How do I check the current balance of my connected bank accounts? +
You can use the get_data_account_balance tool with a specific account_id to retrieve real-time balance information directly from the bank via TrueLayer's Data API.
Does this integration support setting up recurring payments? +
Yes. The create_mandate tool allows you to set up Variable Recurring Payment (VRP) mandates, enabling automated and flexible recurring transfers from your users.
We've already built the connector for TrueLayer. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 13 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.