Invio Xero MCP

nz.co.invioPublished by invio.co.nzOfficial publisherv1.0.0Updated Oct 24, 2026

Every Xero organisation you run, in one AI session. Writes wait for a person to approve them.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP connector that lets an AI assistant work across your Xero organisations in one session, with writes held for human approval.

What you can do
Work across every Xero organisation you run from a single AI session, as described by the provider; no individual tools are listed in the manifest, so specific operations are not documented here. Writes are held until a person approves them, according to the provider's description.
When to use it
Useful if you manage one or more Xero organisations and want an assistant to help with accounting work in the same session, while keeping a human sign-off step before anything is written.
Requirements
A remote endpoint at the provider's site, reached over streamable HTTP. An Invio connector key is required, sent in the X-API-Key header with no prefix; the key is the last part of the connector URL shown once in Settings > MCP > Xero.
Before you install
The connector key is a secret sent as a header; treat it like a password and do not share it. The server can write to Xero data, though the provider says writes wait for human approval. Your Xero organisation data is handled by the third-party provider.

Installation

In SourceWeft

  1. Open Invio Xero MCP in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/nz.co.invio%2Fxero/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "invio-xero": {
      "type": "http",
      "url": "https://www.invio.co.nz/api/xero-mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.