q2

name

q2

description

Q2 offers an integrated digital banking platform enabling financial institutions to manage consumer, small-business, and commercial banking operations, including onboarding, payments, risk/fraud management, analytics, and embedded finance via a unified, scalable solution. Read and write Q2 data through One: users, adminusers, openbankingpayments, customers, achpayments, tactargets and more, 115 actions with real parameter documentation. Use whenever the user asks to look something up in Q2, create or update a record there, or build code against the Q2 API.

Q2 through One

Q2 offers an integrated digital banking platform enabling financial institutions to manage consumer, small-business, and commercial banking operations, including onboarding, payments, risk/fraud management, analytics, and embedded finance via a unified, scalable solution.

One exposes Q2 through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.

How to run an action

1. Find the action in the table below, or call search_one_platform_actions with platform q2 if it is not listed.
2. Call get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
3. Call execute_one_action with parameters copied from that knowledge.

Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.

Before you start

Call list_one_integrations once and confirm Q2 is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.

Each connection carries an access field. If it reports the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.