Maxio MCP

Maxio + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Maxio API. Not affiliated with, endorsed by, or sponsored by Maxio LLC.

[Maxio - MCP server and Claude Code Skill]

_{Full skill page - install, outcomes, safety model.}

Open, local revenue-intelligence CLI for Maxio Advanced Billing - MRR waterfalls, retention, and per-client history computed offline from a SQLite mirror, so the trended history survives even though the live API returns only point-in-time figures. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

Security note (until this connector is reprinted). Do not run HTTP mode (--transport http), not even on localhost. This build has no password, listens on every network interface, and predates the browser-rebinding guard, so a web page you open can reach it. The MCP tools can also make changes with your credentials. Use the default stdio transport. If you set up a tunnel for a remote agent, shut it down. A fix is on the way.

The six agents MSP owners actually use (self-serve, works today):

The ChatGPT desktop app runs maxio-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly and speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: docs/which-agent.md.

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Claude Desktop bundle: the .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion maxio-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or set MAXIO_CLI_PATH to an existing binary). Details: #331.

Download Maxio MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Maxio release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills/plugin install maxio@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Maxio Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/maxio/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/maxio/install.ps1 | iex. Then authenticate per the README and run maxio-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/maxio/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/maxio/install.sh)

The installer drops both maxio-cli (the CLI) and maxio-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

maxio-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/maxio/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/maxio/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update maxio@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see mcp-install.md and docs/which-agent.md for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/maxio --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/maxio --force

Hermes speaks MCP natively, so it can also use the maxio-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the maxio skill from https://github.com/servosity/msp-skills/tree/main/skills/maxio. The skill defines how its required CLI (maxio-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Set the credentials the CLI needs (from your Maxio portal):

MAXIO_PASSWORD=<value> MAXIO_SITE=<value> MAXIO_USERNAME=<value> maxio-cli doctor

doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most Maxio integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking for the MRR movement waterfall and net revenue retention across your entire customer book at board-prep time - because the live API returns only point-in-time figures (and the MRR endpoints require Maxio's Insights/Analytics add-on), with no trended multi-period history to query.

This skill syncs Maxio into a local SQLite mirror with full-text search, and snapshots each sync into a time series. Aggregate questions become one local computation: instant, offline, and the AI sees the answer, not the raw data. Compound commands like maxio-cli mrr waterfall, maxio-cli retention, and maxio-cli reconcile join across subscriptions, customers, components, and invoices - work a stateless API wrapper can't do, and the history keeps growing because the live API has no endpoint that reconstructs historic MRR movement or retention after the fact.

The pain this closes

On Maxio's own G2 reviews, operators name recurring-revenue reporting as the weak spot: MRR, churn, and ARPA are hard to get out cleanly, and teams report having to use third-party applications on imported billing data to answer them. Even a basic ask - the customers who signed up in a given window and the revenue they brought - has no clean portal answer, and the live API returns only point-in-time figures, with no endpoint to reconstruct the historic trend.

This skill closes that gap from the terminal or your AI agent:

• maxio-cli mrr waterfall --since 2026-01-01 --group-by month - the New/Expansion/Contraction/Churn/Reactivation movement, monthly.
• maxio-cli retention --since 2026-01-01 --group-by month - net and gross revenue retention, plus quick ratio.
• maxio-cli new-customers --since 3m - new logos in the window and the MRR they brought.
• maxio-cli triage --limit 20 - the accounts that need attention right now.
• maxio-cli reconcile --since 2026-01-01 - where normalized MRR diverges from what was actually invoiced.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way maxio-mcp runs, and shares MCP configuration with Codex (OpenAI): add maxio-mcp under Settings > MCP servers as a STDIO server, or add it once to Codex's ~/.codex/config.toml. ChatGPT on the web is not supported by msp-skills yet: it needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted; the security note in mcp-install.md explains why. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Does this work with Codex, Cursor, Windsurf, Cline, Copilot, or Gemini?

Yes - all of them speak MCP. Cross-tool install commands are in the matrix above and the deep-dive in docs/which-agent.md.

Do I need to know how to code?

No. The recommended install is to paste one sentence into Claude Code or Codex - your agent reads SKILL.md and does the install. The fallback is a one-line installer per OS (bash or PowerShell). Neither path requires writing code. You'll enter your Maxio credentials once.

Is my Maxio data safe?

Your data stays on your machine. The CLI and MCP server are local binaries. The SQLite mirror sits in a directory under your user account. The AI agent only sees what the CLI returns - typically a query result, not raw bulk data. Credentials are read from your environment or your agent's config; never bundled into this repo or transmitted anywhere by MSP Skills.

Will this hit my Maxio API rate limits?

Rarely, for the analytics. After you sync, the revenue-analytics commands (maxio-cli mrr waterfall, maxio-cli retention, maxio-cli cohort, maxio-cli triage, maxio-cli reconcile) read from the local SQLite mirror, so they make zero API calls. Keeping the mirror current is two incremental commands - maxio-cli sync for the full dataset and maxio-cli mrr sync to snapshot MRR-movement history - and both fetch only what changed since the last run. A sync narrowed by a --param, --global-param or --resource-param, or by a --since later than the last full pass, reads what you asked and leaves the stored sync time alone, so the next plain sync still fetches everything since that pass. The endpoint-mirror commands and maxio-cli tail read live from Maxio, so those do count against your limits.

Do I need to be a Maxio partner or customer?

You need your own Maxio Advanced Billing API credentials (a username and password) - that's it. This is an unofficial, community-built skill, not a Maxio product, so there is no partner program or separate signup. It reads only the data your credentials already grant.

Will this replace my Maxio portal?

No. It complements the portal, which still owns billing operations and configuration. This skill gives your AI agent fast, trended revenue answers and keeps a local copy of the history that the live API can no longer reconstruct.

What does it cost?

Free. Apache-2.0 licensed. You pay only for whichever AI agent you use (Claude, ChatGPT, Codex, etc.), and that's billed by your AI provider, not by us.

Credential safety

• The API key travels only as HTTP Basic (<key>:x) and only to the scheme, host and port of the configured base URL (https://<site>.chargify.com built from MAXIO_SITE, or MAXIO_BASE_URL). The one other host is Maxio's Events-Based Billing ingestion endpoint, https://events.chargify.com/<the same site>/events/..., used by events record and bulk-record-events. A redirect to any other host, a plain http address and a site that is not a single host-name label are all refused, so the key never reaches them. MAXIO_SITE has no default: with it unset, a command names the variable and sends nothing.
• A response's card, bank and token fields (a vault token, a self-service page token, a webhook signature, a Maxio.js chargify_token) are replaced with [redacted] as the response arrives, so ordinary lists still work and none of those values reach the output or the local store.
• Any other output, file or MCP result that would repeat MAXIO_API_KEY, the stored key, or a credential you typed (a card number or CVV, a bank account number or IBAN, a chargify_token, a payment nonce) is withheld as a whole and prints [credkit: withheld from <where>: it carried a credential this program holds] in its place, including in the common encodings.
• Responses are never cached on disk: every command reads the API's current answer.
• A saved key lives only in credentials.toml, or in a config.toml you put it in, and both are kept at mode 0600. auth set-token reads the key from stdin, never from an argument.
• --dry-run sends nothing. Over MCP, maxio_execute (every Maxio endpoint that changes something) and import return a preview and send only with confirm: true, and a tool argument can never name a file to read or write.

Safety model

The strongest control is the scope you grant the Maxio credentials - the CLI can only do what the credentials are permitted to do. Full details, including how to lock it down, are in governance.md.

Status

Beta. Validated against the Maxio API surface and being validated with MSPs running it live against their own production tenant in our weekly Build Sessions. RSVP at compoundingteams.com/build-sessions.

Standards. Conforms to the open Agent Skills spec (Anthropic, Dec 2025; 40+ agents). MCP-compatible - works with any MCP-capable agent including Hermes. OpenClaw-ready (frontmatter pre-wired, awaiting OpenClaw launch).

Maintained by Servosity. Apache-2.0 licensed. Built with CLI Printing Press. Last updated: 2026-06-30.