Xero
OCI · GHCR.IO/WYRE-AI/XERO-MCP
MCP server for Xero accounting — contacts, invoices, payments, accounts, and financial reports.
Available components
Last scanned (4 hours ago)
Scores higher than 61% of OCI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1435 tokens (~68/item across 21 items; 20 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 15 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Capabilities: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 9
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/xero-mcp@v1.5.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
xero_accounts_get ~35
Get detailed information about a specific account by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | The unique account ID (UUID) |
No output schema declared.
No examples provided.
xero_accounts_list ~115
List chart of accounts in Xero. Optionally filter by account type or class.
| Name | Type | Req | Description |
|---|---|---|---|
| Class | string | – | Filter by account class |
| Type | string | – | Filter by account type (e.g., "BANK", "REVENUE", "EXPENSE", "CURRENT", "FIXED", "EQUITY", "CURRLIAB", "TERMLIAB", "DIRECTCOSTS", "OVERHEADS", "DEPRECIATN", "OTHERINCOME", "SALES") |
No output schema declared.
No examples provided.
xero_back ~26
Return to domain selection (no-op in flattened mode). All tools are always available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xero_contacts_create ~145
Create a new contact in Xero. Name is required; other fields are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| AccountNumber | string | – | Account number for the contact |
| EmailAddress | string | – | Contact email address |
| FirstName | string | – | Contact first name |
| IsCustomer | boolean | – | Whether the contact is a customer |
| IsSupplier | boolean | – | Whether the contact is a supplier |
| LastName | string | – | Contact last name |
| Name | string | yes | Contact name (required) |
| Phone | string | – | Contact phone number |
| TaxNumber | string | – | Tax number (ABN in Australia, GST in NZ, VAT in UK) |
No output schema declared.
No examples provided.
xero_contacts_get ~48
Get detailed information about a specific contact by its ID. Returns full contact profile including addresses, phone numbers, and email.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | string | yes | The unique contact ID (UUID) |
No output schema declared.
No examples provided.
xero_contacts_list ~86
List contacts in Xero with pagination. Optionally filter using a where clause. Returns contact details including name, email, and addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number (1-based, default: 1). Each page returns up to 100 contacts. |
| where | string | – | Optional Xero where clause filter (e.g., 'ContactStatus=="ACTIVE"') |
No output schema declared.
No examples provided.
xero_contacts_search ~38
Search contacts by name. Returns contacts whose name contains the search term.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | Search term to match against contact names |
No output schema declared.
No examples provided.
xero_invoices_create ~157
Create a new invoice in Xero. Requires type, contact, and at least one line item.
| Name | Type | Req | Description |
|---|---|---|---|
| ContactID | string | yes | The contact ID to create the invoice for (required) |
| Date | string | – | Invoice date in YYYY-MM-DD format |
| DueDate | string | – | Due date in YYYY-MM-DD format |
| LineItems | array | yes | Array of line items (required). Each item needs Description, Quantity, UnitAmount, and AccountCode. |
| Reference | string | – | Invoice reference/PO number |
| Status | string | – | Initial invoice status (default: DRAFT) |
| Type | string | yes | Invoice type: ACCREC (sales invoice) or ACCPAY (bill) (required) |
No output schema declared.
No examples provided.
xero_invoices_get ~50
Get detailed information about a specific invoice by its ID. Returns full invoice details including line items, amounts, and payment status.
| Name | Type | Req | Description |
|---|---|---|---|
| invoiceId | string | yes | The unique invoice ID (UUID) |
No output schema declared.
No examples provided.
xero_invoices_list ~105
List invoices in Xero with pagination. Optionally filter by status and type (ACCREC for sales, ACCPAY for bills).
| Name | Type | Req | Description |
|---|---|---|---|
| Status | string | – | Filter by invoice status |
| Type | string | – | Filter by invoice type: ACCREC (accounts receivable / sales invoices) or ACCPAY (accounts payable / bills) |
| page | number | – | Page number (1-based, default: 1). Each page returns up to 100 invoices. |
No output schema declared.
No examples provided.
xero_invoices_update_status ~60
Update the status of an existing invoice. Can submit, authorise, or void an invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| Status | string | yes | New status for the invoice (required) |
| invoiceId | string | yes | The invoice ID to update (required) |
No output schema declared.
No examples provided.
xero_navigate ~152
Discover available Xero tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to explore: - contacts: Contact management - list, get, create, and search contacts (customers and suppliers) - invoices: Invoice management - list, get, create invoices and update their s… |
No output schema declared.
No examples provided.
xero_payments_create ~100
Create a new payment in Xero. Records a payment against an invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| AccountID | string | yes | The bank account ID the payment is made from/to (required) |
| Amount | number | yes | Payment amount (required) |
| Date | string | yes | Payment date in YYYY-MM-DD format (required) |
| InvoiceID | string | yes | The invoice ID to apply the payment to (required) |
| Reference | string | – | Payment reference |
No output schema declared.
No examples provided.
xero_payments_get ~36
Get detailed information about a specific payment by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentId | string | yes | The unique payment ID (UUID) |
No output schema declared.
No examples provided.
xero_payments_list ~62
List payments in Xero with pagination. Optionally filter by status.
| Name | Type | Req | Description |
|---|---|---|---|
| Status | string | – | Filter by payment status |
| page | number | – | Page number (1-based, default: 1). Each page returns up to 100 payments. |
No output schema declared.
No examples provided.
xero_reports_aged_payables ~43
Get an Aged Payables report showing outstanding supplier bills by age.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Report date in YYYY-MM-DD format (required) |
No output schema declared.
No examples provided.
xero_reports_aged_receivables ~45
Get an Aged Receivables report showing outstanding customer invoices by age.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Report date in YYYY-MM-DD format (required) |
No output schema declared.
No examples provided.
xero_reports_balance_sheet ~38
Get a Balance Sheet report as of a specific date.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Report date in YYYY-MM-DD format (required) |
No output schema declared.
No examples provided.
xero_reports_profit_and_loss ~61
Get a Profit and Loss (income statement) report for a date range.
| Name | Type | Req | Description |
|---|---|---|---|
| fromDate | string | yes | Start date in YYYY-MM-DD format (required) |
| toDate | string | yes | End date in YYYY-MM-DD format (required) |
No output schema declared.
No examples provided.
xero_status ~16
Show credentials status and available domains
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Xero MCP server?
Xero runs locally as a container image, launched with docker run --rm -i -e XERO_TENANT_ID -e XERO_ACCESS_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/xero-mcp:v1.5.7. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-ai/xero-mcp
claude mcp add wyre-ai-xero-mcp -- docker run --rm -i -e XERO_TENANT_ID -e XERO_ACCESS_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/xero-mcp:v1.5.7
This image reads XERO_TENANT_ID, XERO_ACCESS_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Xero MCP server?
Xero is an MCP server listed in the public MCP registry as io.github.WYRE-AI/xero-mcp. MCP server for Xero accounting, contacts, invoices, payments, accounts, and financial reports. This page covers its container image (ghcr.io/wyre-ai/xero-mcp).
Is the Xero MCP server safe to use?
Xero scores 43 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Xero MCP server expose?
Xero exposes 20 tools: xero_navigate, xero_status, xero_back, xero_contacts_list, xero_contacts_get, and 15 more. Their descriptions and schemas cost roughly 1,418 tokens of context every time the server is loaded.
Is the Xero MCP server still maintained?
Xero is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Xero MCP server under?
Xero declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.