--- title: "Qualy MCP server — Manage student payments through your AI assistant" description: "Connect Claude, ChatGPT, or any MCP-aware assistant to Qualy. Find students, draft payment plans from an offer letter, chase overdue tuition and invoice partners — in plain English, with you approving the writes." lastModified: "2026-07-17" lang: "en" wordCount: 1714 url: https://qualyhq.com/mcp --- ## Site navigation - [For schools](/international-education/for-schools.md) — For international education schools - [For agents](/international-education/for-education-agents.md) — For international education agents - [Explore](/training.md) — Watch videos on how to use Qualy - [About](/about.md) — Learn about Qualy's mission and values - [Pricing](/pricing) - [5-min demo](/demo.md) - [Login](https://dashboard.qualyhq.com) # Qualy MCP server — Manage student payments through your AI assistant > Ask your AI assistant — in plain English — to find a student, draft a payment plan from an offer letter, chase overdue tuition or invoice a partner. The assistant does the work; you approve anything that writes. **Connect Claude or ChatGPT to Qualy.** - [Get started](/contact-us.md) - [Read the docs](https://docs.qualyhq.com/docs/mcp-server) **Example.** A user asks: "Camila Soares just accepted her Monash offer — set up her tuition from the fee schedule I uploaded." — the assistant calls `extract_payment_plan_from_file`, `find_contact`, `create_payment_plan`. ## Bring your own assistant. Point any MCP-aware assistant at the Qualy endpoint, sign in with a scoped API key, and your team can start asking it to look up students, draft plans and invoice partners today. - **Claude** — Works with Claude Desktop, Claude in the browser, and Claude Code. Anthropic authored the protocol, so the experience is first-class. - **ChatGPT** — Works with the ChatGPT desktop and web apps, custom GPTs, and the OpenAI Agents SDK — all of which gained MCP support through 2025. **And any other MCP-compliant client:** Cursor, Windsurf, Zed, Block's Goose, Continue.dev, Custom agents (TypeScript · Python · SDKs). _MCP is an open protocol; client names are nominative use only. Qualy doesn't endorse, partner with, or co-market any client listed here. If your assistant speaks MCP, it can speak to Qualy._ ## Eleven tools. Your whole back office. The MCP server hands your assistant the same records the Qualy dashboard runs on — students, payments, plans, partners and commissions — as typed, named tools it can call. ### Students & contacts (2 tools) Find the right person before you act, or add a new one. - `find_contact` — Search students, payers and agents by name, email or phone. - `save_contact` _(write)_ — Add a new student, lead or payer. ### Payments & plans (5 tools) Raise a single request, or a full plan read straight from a document. - `create_payment` _(write)_ — Raise a single payment request for a student. - `create_payment_plan` _(write)_ — Build a full plan: services, orders and instalments. - `extract_payment_plan_from_file` — Read an offer letter or fee schedule into a draft plan. - `analyze_file` — Pull structured data out of an uploaded document. - `check_payments` — How much tuition is due, overdue, paid or failed. ### Partners & commissions (4 tools) Invoice the agents and institutions you work with, and track payouts. - `create_partner` _(write)_ — Add an agent, institution or supplier. - `invoice_partner` _(write)_ — Raise an RCTI or tax invoice for a partner. - `check_invoices` — Partner payouts: due, pending review or paid. - `check_invoice_status` — Look up a specific split, invoice or payout. _**write** tools create or change records. Most MCP clients prompt you before running them — and none of them move money on their own._ _In Qualy's API these are contacts, payment intents, orders, partnerships and payment splits — the same records the dashboard uses, now callable by your assistant._ ## Conversation instead of clicks. Your team asks in plain language instead of clicking through the dashboard. The assistant blends Qualy with everything else it can see — your email, calendar, files — plus its own reasoning, in one answer. The cards below are illustrative. - **Education agent:** "Which of my agents are still owed commission this month?" _(calls `check_invoices(status: "pending")`)_ - **Finance:** "How much student tuition is overdue right now?" _(calls `check_payments(status: "overdue")`)_ - **Education agent:** "Invoice Sydney English College AUD 2,400 for Lucas's commission." _(calls `invoice_partner(partnership: "Sydney English College", amount: 2400)`)_ - **Education agent:** "Set up João’s payments from the fee schedule I just uploaded." _(calls `extract_payment_plan_from_file(fileId: ...)`, `create_payment_plan(contact: "joao@...", suggestions: ...)`)_ - **Operations:** "Pull up Mariana's payment history." _(calls `find_contact(query: "Mariana")`, `check_payments(contact: ...)`)_ - **Education agent:** "Add Cambridge Language Institute as a new partner." _(calls `create_partner(name: "Cambridge Language Institute", type: "supplier")`)_ ## Your assistant drafts. You and Qualy stay in control. Moving money for international students is regulated work. The MCP server lets an assistant do the busywork — search, draft, raise requests — while every write is yours to approve and the money itself only ever moves through Qualy's controls. - **01 — Nothing moves money on its own.** create_payment and create_payment_plan raise payment requests that students pay through a secure Qualy link; invoice_partner raises an invoice. The assistant never debits an account or releases a payout — reconciliation, FX and payouts run on the Qualy platform, exactly as they do from the dashboard. - **02 — Writes wait for a human.** Tools that change data are marked as writes. Most MCP clients prompt you to approve each one before it runs, and you can scope an API key to read-only to switch writes off entirely. - **03 — Scoped API keys.** Each connection authenticates with a Qualy API key you mint and can revoke. Scope it read-only, to a single sub-account, or to specific tools. - **04 — Audit trail by default.** Every tool call is logged with the agent identity, the prompt behind it, the tool name and its arguments — the same regulated record the dashboard keeps. - **05 — No card or full bank data through the model.** Card numbers are never stored by Qualy and never reach the MCP server. Bank details only surface in the tools your key explicitly allows. _Operated by Qualy Services OÜ. Compliance, KYC and reconciliation run on the Qualy platform and its licensed payment partners — regardless of how a record is created._ ## Ask in plain English. Qualy does the rest. An assistant is the quickest way to ask Qualy a question or kick off a task. The hard part — **reconciliation, commission splits, FX across 141 currencies, RCTIs and partner payouts** — is built into the platform and runs on its own, whether or not an assistant is in the loop. - **100%** — payments auto-reconciled - **141** — currencies settled - **Instant** — commission payouts - **11** — tools, one endpoint - [See how Qualy automates payments](/demo.md) ## The same surface, as a REST API. Every MCP tool here runs on Qualy's public API — the one our own dashboard uses. If your team has engineers and owns the product surface, skip the assistant and call it directly. - [Explore the Qualy API](/api.md) ## Point-and-click automation? Use Zapier. For deterministic workflows you can describe up front — a deal closes → raise an invoice, a payment lands → append a row — Zapier wires Qualy to 7,000+ apps with no assistant and no code. - [See the Zapier integration](/zapier.md) ## Frequently asked questions What the Qualy MCP server is, what it does today, and where it sits next to our REST API and Zapier integration. ### What is MCP, and why does Qualy support it? MCP — the Model Context Protocol — is an open standard published by Anthropic in late 2024 for connecting AI assistants to external tools and data. By running an MCP server, Qualy lets any MCP-aware assistant (Claude, ChatGPT, Cursor and others) work with your payment back office through typed tool calls — without anyone building a bespoke integration. We support it because student-payment admin is exactly the kind of repetitive back-office work assistants handle well under human approval. ### Is the Qualy MCP server available today? Yes — it's live for Qualy customers. Point your assistant at the Qualy endpoint, authenticate with a scoped API key, and it can start calling the tools above. Talk to our team and we'll help you connect your first assistant. ### Which AI assistants can use it? Any MCP-compliant client — Claude (Anthropic), ChatGPT (OpenAI), Cursor, Windsurf, Zed, Block's Goose, Continue.dev, and any custom agent built on the official MCP SDKs. The same Qualy endpoint and the same API-key auth flow; only the host changes. ### Can the assistant move money on its own? No. The write tools create records — a payment request, a plan, an invoice, a partner — they don't move funds. Students pay through a secure Qualy link, and reconciliation, FX and payouts run on the Qualy platform regardless of how the record was created. Most MCP clients also prompt for approval before any write, and you can scope your API key to read-only to disable writes entirely. ### How is this different from the Qualy API? They run on the same endpoints. The REST API is for engineering teams who want to build a payment flow inside their own product. The MCP server is for teams whose interface is already an AI assistant — they want their agent to read and write into Qualy without writing or maintaining glue code. Plenty of teams use both. ### How is this different from the Qualy Zapier integration? Zapier is point-and-click, no-code automation between Qualy and 7,000+ apps — event-driven and deterministic. MCP is conversational tool-use by an assistant — natural language in, structured tool calls out, with the model deciding which tools to call in what order. Zapier suits a fixed workflow you can describe up front; MCP suits the long tail of one-off questions and instructions you give an assistant. ### How are API keys and permissions handled? Each MCP connection presents a Qualy API key you mint and can revoke at any time. Keys can be scoped read-only, limited to a sub-account, or restricted to specific tools. The server checks the scope on every tool call before it runs — there's no separate auth system, it reuses the same authenticated surface as the dashboard. ### What about compliance, KYC and reconciliation? Unchanged. Every control that runs on the Qualy platform today runs in front of every MCP tool call. An assistant can't route around them — it can only request actions Qualy then evaluates. Reconciliation, FX, commission splits and payouts stay on the platform side. ### Does the MCP server cost anything extra? No additional Qualy fee — it's included with your account, like the REST API and the Zapier integration. The cost of the AI assistant itself sits with whoever provides it (Anthropic, OpenAI, or your own deployment). ### How do I get started? Talk to our team and we'll switch the MCP server on for your account and help you connect your first assistant. Tell us which assistant you want to point at it and the workflows you're trying to support. ## Light-speed payments & commissions. The faster, smoother way to manage payments — for you, your students, and your partners. Now something your AI assistant can speak to. - Start with a pilot with no strings attached - Implementation & training included - Transparent fees - [Contact sales](/contact-us.md) - [Book a demo](/demo/schedule.md) ## More on Qualy **Industries** - [For schools](/international-education/for-schools.md) — For international education schools - [For agents](/international-education/for-education-agents.md) — For international education agents **Support** - [Training](/training.md) - [System status](https://qualyhq.statuspage.io/) — Qualy system status - [Product updates](https://changelog.qualyhq.com) — As we work on Qualy, here we spotlight what we’ve learned and updated across our products - [Contact](/contact-us.md) **Product** - [Demo](/demo.md) - [Enterprise](/enterprise.md) - [Testimonials](/testimonials.md) — Learn what some customers have to say about Qualy - [About](/about.md) — Learn about Qualy's mission and values - [Blog](/blog) — International education payments blog by Qualy - [Trust center](/trust.md) - [API](/api.md) — Qualy API for international education payments - [Zapier](/zapier.md) — Connect Qualy to 7,000+ apps with Zapier - [NexPay](/nexpay.md) — Qualy + NexPay — automate everything around the payment **Legal** - [General terms](/terms-and-conditions.md) - [Payer terms](/terms-for-payers.md) - [Privacy policy](/privacy-policy.md) - [BECS DDR](/becs-dd-service-agreement.md)