xero-connect

Configure Xero OAuth 2.0 MCP integration with browser-based authentication and Vault token storage.

4|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/MattVOLTA/outworkos_diy --skill xero-connect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: xero-connect
Source: https://github.com/MattVOLTA/outworkos_diy/tree/main/skills/xero-connect
Command: npx skills add https://github.com/MattVOLTA/outworkos_diy --skill xero-connect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sets up and maintains the Xero OAuth 2.0 MCP integration across projects, handling app creation, credentials, MCP config, and verification.

Core Features & Use Cases

  • Secure OAuth 2.0 browser-based authentication flow for Xero MCP across projects.
  • Centralized token storage and rotation via Vault at a shared location.
  • Automated MCP configuration generation and verification, with guidance for re-authentication when tokens expire.

Quick Start

Run the xero-auth.sh script to authenticate with Xero and store tokens locally.

Frequently Asked Questions about xero-connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up OAuth 2.0 authentication for Xero MCP integration?▼

To set up Xero OAuth 2.0 authentication, run the xero-auth.sh script to trigger a browser-based auth flow, storing tokens locally and updating .mcp.json configurations securely via Vault.

Why does my Xero MCP integration stop working after token expiry?▼

Xero MCP integration stops working after token expiry because OAuth 2.0 tokens require rotation. Re-authenticate by running xero-auth.sh again to refresh and store new tokens in Vault.

How does Vault handle Xero token storage and management?▼

Vault handles Xero token storage by centralizing token management at a shared location, requiring XERO_CLIENT_ID and XERO_CLIENT_SECRET to securely store and rotate authentication tokens.

Do I need XERO_CLIENT_ID and XERO_CLIENT_SECRET for MCP configuration?▼

Yes, you need XERO_CLIENT_ID and XERO_CLIENT_SECRET stored via Vault to generate automated MCP configurations and perform browser-based authentication for the Xero integration.

What's the best way to troubleshoot MCP errors during Xero authentication?▼

The best way to troubleshoot Xero MCP authentication errors is to verify .mcp.json configurations and ensure valid XERO_CLIENT_ID and XERO_CLIENT_SECRET in Vault before re-running xero-auth.sh.