# Xero (npm · @pipeworx/mcp-xero)

Xero (Accounting) MCP Pack

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-xero/xero-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-xero/xero-mcp)
- npm · `@pipeworx/mcp-xero`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-xero/pipeworx-mcp-xero.md), [page](https://verifymcp.io/servers/pipeworx-io-xero/pipeworx-mcp-xero)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-xero`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-xero).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 675 tokens (~135/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Xero MCP server?

Xero runs locally as an npm package, launched with npx -y @pipeworx/mcp-xero. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-xero -- npx -y @pipeworx/mcp-xero
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-xero": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-xero"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-xero": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-xero"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-xero -- npx -y @pipeworx/mcp-xero
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-xero": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-xero"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-xero --command npx --arg -y --arg @pipeworx/mcp-xero
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-xero:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-xero"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-xero": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-xero"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-xero -t stdio -c npx -a -y @pipeworx/mcp-xero
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-xero": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-xero"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (5)

### `list_organisations` (~68 tokens)

List the Xero organisations (tenants) the connected account can access, with tenant id, name, and type. Xero accounting is multi-tenant — use this first to discover the tenant_id for a specific organisation, then pass it to the other accounting tools to target that org.

### `list_invoices` (~168 tokens)

List invoices and bills from a Xero accounting organisation. Returns compact invoice summaries (number, type, status, contact, dates, total, amount due, currency) for bookkeeping, accounts-receivable, and accounts-payable review. Supports Xero filter expressions and pagination.

Input parameters:

- `page` (number): Page number for pagination (default 1). Xero returns up to 100 invoices per page.
- `tenant_id` (string): Optional Xero tenant (organisation) id to target. If omitted, the first connected organisation is used. Get ids from list_organisations.
- `where` (string): Optional Xero filter expression (e.g. 'Status=="AUTHORISED"' or 'Type=="ACCREC"'). Applied as the Xero `where` query parameter.

### `list_contacts` (~160 tokens)

List contacts (customers and suppliers) from a Xero accounting organisation. Returns name, email, status, and customer/supplier flags. Use for accounting, bookkeeping, and accounts-receivable/payable workflows. Supports Xero filter expressions and pagination.

Input parameters:

- `page` (number): Page number for pagination (default 1). Xero returns up to 100 contacts per page.
- `tenant_id` (string): Optional Xero tenant (organisation) id to target. If omitted, the first connected organisation is used. Get ids from list_organisations.
- `where` (string): Optional Xero filter expression (e.g. 'IsCustomer==true' or 'ContactStatus=="ACTIVE"'). Applied as the Xero `where` query parameter.

### `get_profit_and_loss` (~141 tokens)

Get the Profit and Loss (income statement) financial report from a Xero accounting organisation for an optional date range. Returns the structured Xero report (report name, date, and row sections covering revenue, expenses, and net profit). Use for financial reporting and bookkeeping analysis.

Input parameters:

- `from_date` (string): Optional start date of the reporting period in YYYY-MM-DD format.
- `tenant_id` (string): Optional Xero tenant (organisation) id to target. If omitted, the first connected organisation is used. Get ids from list_organisations.
- `to_date` (string): Optional end date of the reporting period in YYYY-MM-DD format.

### `list_accounts` (~86 tokens)

List the chart of accounts from a Xero accounting organisation. Returns each account's code, name, type, class, and status. Use to understand an organisation's general ledger structure for bookkeeping and financial reporting.

Input parameters:

- `tenant_id` (string): Optional Xero tenant (organisation) id to target. If omitted, the first connected organisation is used. Get ids from list_organisations.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-xero/pipeworx-mcp-xero#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Xero MCP server?

Xero is an MCP server listed in the public MCP registry as io.github.pipeworx-io/xero. Xero (Accounting) MCP Pack. This page covers its npm package (@pipeworx/mcp-xero).

### Is the Xero MCP server safe to use?

Xero scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 5 tools: list_organisations, list_invoices, list_contacts, get_profit_and_loss, list_accounts. Their descriptions and schemas cost roughly 623 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 5 November 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 MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-xero
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-xero
- Repository: https://github.com/pipeworx-io/mcp-xero
- Website: https://pipeworx.io/packs/xero
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-xero/pipeworx-mcp-xero.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-xero/pipeworx-mcp-xero.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-xero/pipeworx-mcp-xero