Zuora MCP server: what it reads, what it changes, and how to connect Claude or ChatGPT

Zuora offers an official MCP server, hosted per region or run locally via npm, that reads and writes billing, payments and revenue data under OneID OAuth. Verified 21 Oct 2026.

Official remote MCP server · read and write (hosted by Zuora)
Official local MCP server (npm zuora-mcp) · read and write

Hosting: Remote HTTP hosted by Zuora per region, e.g. https://na.zuora.com/mcp, https://eu.zuora.com/mcp, sandbox https://apisandbox.zuora.com/mcp. Local stdio via npm package zuora-mcp.
Auth: Remote: OAuth 2.0 through Zuora OneID, one client ID and secret per MCP client. Local: a Zuora user's OAuth client credentials.
Read / write: Read and write. Per Zuora, 91 tools: 18 read, 37 write, 36 mixed. Writes need a tenant AI level that allows them.
Works with: Claude.ai, Claude Desktop, Claude Code, ChatGPT, Cursor, Windsurf, Codex, VS Code, any MCP client
Plan requirement: Zuora AI must be enabled on the tenant by a OneID Organization Administrator; Zuora doesn't state an edition or price
Last changed: 2026-10-08 (MCP docs updated with per-region endpoints and client setup guides)
Verification: Verified 21 Oct 2026 by theFinanceStack · confidence: high

What can an agent do with Zuora through MCP?

It queries billing, payment, usage and revenue data. Where the tenant allows writes, it can also create and change those records.

Zuora says the 91 tools cover more than 330 operations.

Tool families

Families include:

Family	Tools
Query and reporting	8
Billing and subscriptions	11
Invoicing and receivables	7
Payments	5
Revenue	28

How writes behave

Zuora doesn't say whether MCP writes create drafts. Its local package README says operations have executed immediately since version 1.0.0. Treat every write as live.

Tools that move or settle money

manage_payments: create, apply, unapply, cancel, refund and transfer payments. Refunds are issued here.
manage_payment_runs
manage_payment_schedule_items: retry, cancel, skip
Write-offs through manage_invoices and manage_debit_memos
manage_credit_memos: post, apply, reverse

Good to know

manage_refunds only updates, cancels or deletes existing refunds.
manage_invoices can also email invoices to customers.

Can

Query objects, run reports and look up accounts, subscriptions, invoices, payments and usage (read)
Answer product and API questions and generate code (read)
Create and change subscriptions, orders, products and customer accounts (write)
Post and apply credit memos; write off invoices and debit memos (write)
Create, apply, refund and transfer payments; start payment runs (write, moves money)
Run revenue journal runs, holds and forecasts; manage workflows and settings (write)

Cannot

Write anything while the tenant is set to Read-Only (per Zuora; for the local package, from version 1.0.0 only)
Enforce per-action approval for MCP writes; Zuora leaves that to the client (per Zuora)
Exceed the permissions of the user who authorised it (per Zuora)

What access does it get?

It acts as the authorising user, capped by the tenant's AI level. Zuora publishes no OAuth scope names.

Where	Scopes and permissions (as documented)	Admin requirement
Remote MCP server (hosted)	No scope names documented. Access follows the user who signs in through OneID, capped by the tenant AI level: Read-Only exposes read tools; Supervised (called Read-Write on the enable page) or Autonomous (named in the tools reference) adds writes. Zuora's Supervised approval step doesn't apply to MCP writes; per Zuora, the connected client enforces approval.	A OneID Organization Administrator enables AI per tenant (Admin Console › AI); OneID admin access is needed to create the OAuth client
Local MCP server (npm zuora-mcp)	No scope names documented. The local server inherits the permissions of the Zuora user whose OAuth client it uses, capped by the tenant AI level from version 1.0.0. Per the README, 1.0.0-beta.7 and earlier don't apply that cap. Zuora's steps create the client on the administrator's own user record, so by default it runs with that administrator's permissions.	A Zuora administrator creates the OAuth client on their own user record (Settings › Administration › Manage Users › your user › OAuth Clients)

How do I connect it?

Enable Zuora AI, create a OneID OAuth client for your MCP client, then add your region's endpoint and sign in through OneID.

In OneID, an Organization Administrator enables AI for the tenant (Admin Console › AI). Choose Read-Only unless you need writes.
In OneID go to Settings › Manage OAuth 2.0 Clients › + New: Authorization Code, type MCP Client, application Billing, redirect URI https://claude.ai/api/mcp/auth_callback. Save the client ID and secret.
In Claude go to Settings › Connectors › Add custom connector, enter your endpoint (e.g. https://na.zuora.com/mcp) and put the client ID and secret under Advanced settings.
Sign in, pick your tenant on the OneID consent page, then use Configure to set per-tool permissions.

Zuora has no Claude directory listing. Team/Enterprise: an Owner adds custom connectors.

What should a finance team watch for?

Zuora says it does not enforce approval for MCP writes, so the client's prompts are the only check before live changes.

Zuora leaves write approval to the client, so keep confirmation prompts on. The local package dropped its approval tool in version 1.0.0. The README says pinning zuora-mcp@1.0.0-beta.7 keeps it, but that beta doesn't apply the tenant AI level, so Read-Only won't block its writes.
Payment, refund, write-off and credit memo tools can move or settle money. Keep the tenant on Read-Only unless a reviewed workflow needs writes, and run the local package at 1.0.0 or later so that setting applies.
Invoice comments and account notes are free text. An injected instruction there could push an agent to refund, write off, post or email invoices to customers, so approve each write yourself.
Local server: the client secret sits in plain text in the client config, often synced or shared. Don't commit it; use the client's secret storage where available.
Local server: by default it runs with the permissions of the administrator who created the OAuth client. Consider a dedicated least-privilege Zuora user, and pin an exact package version so updates can't change write behaviour silently.
Two production entries on Zuora's endpoint page show link text that differs from the URL; confirm yours with Zuora.
Zuora says its AI services reach Zuora systems over private VPC connections. It makes no training or retention statement for MCP.
Zuora documents no rate limits or result caps for MCP queries. Check large pulls against Zuora's own reports.

How could finance teams and accounting firms use it?

On Read-Only it suits billing questions and reporting. With writes on, use it to prepare changes that a person approves call by call.

Inside a company

Ask for top accounts by MRR, large open invoices or recent payments without building a report.
List customers with the most unbilled usage before a bill run and flag anything unexpected.
Explain a month's revenue movement from Zuora's revenue reports, if your tenant uses Zuora for revenue recognition.
Prepare subscription amendments or credit memos for a billing lead to approve one call at a time.

At an accounting firm

Pull a client's Zuora invoices and payments by period to reconcile against a general ledger export.
Review a client's credit memos, write-offs and refunds for the period before sign-off.
Check revenue holds and journal runs during a revenue recognition review.
Test proposed pricing changes on a sandbox endpoint before production.

Whatever the use, keep a person approving anything that changes Zuora or your ledger, and treat agent figures as drafts until they tie to Zuora's reports.

Want Zuora connected to Claude for your team?

We configure scoped connections and a review step before anything changes your books. Fixed fee.

Book a 30-minute setup call

Change log

Date	Change	Source
Undated	Local package zuora-mcp 1.0.0 removed the approval tool (operations execute immediately) and began applying the tenant AI level. Pinning 1.0.0-beta.7 keeps the approval tool without that cap	cdn.jsdelivr.net/npm/zuora-mcp/README.md
2026-10-08	Zuora MCP docs updated: per-region endpoints, redirect URIs, Claude and ChatGPT setup guides, 91-tool reference	docs.zuora.com/en/zuora-ai/zuora-mcp-server/zuora-mcp-server

FAQ

Is this official?

Yes. Zuora documents both the hosted and the local server in its own product docs, and publishes the local server as the npm package zuora-mcp.

Is it free?

Zuora doesn't state a price or edition for MCP. It requires Zuora AI to be enabled on the tenant; ask Zuora whether your contract includes it.

Does it change data in Zuora?

It can. Per Zuora, 73 of the 91 tools are write or mixed, including payments, refunds and credit memos. On Read-Only it only reads.

Is my data used to train models?

Zuora's MCP and AI administration pages make no training or retention statement. Check Zuora's terms and your AI provider's terms before connecting.

Can my accountant use it on my behalf?

Zuora doesn't address this. Access follows the user who authorises the connection, so an accountant would connect with a Zuora user on your tenant that has the permissions you choose to grant.

Something wrong or out of date? Tell us and we'll email you when it's fixed.

Sources

Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.