These plugins are part of XBert.
Every workflow here also lives as a screen inside the XBert app. Same data, same rules, same audit trail — two ways in.
One product, two surfaces
Install once. Slash-command everything.
Add the XBert MCP and the plugins. Slash commands like /anomaly-review, /config-audit and /workflow-review run the same workflow XBert runs internally, with audit-ready output dropping into your file system or back into the chat.
- Best for
- ad-hoc requests, exploratory questions, batch tasks across many clients
- Lives in
- Claude Code or Claude Desktop
- Connects via
- MCP
- What you get
- the full XBert tool catalogue (200 tools) + 4 calibrated plugins
Open XBert. See the same workflows as first-class screens.
Every slash command maps to a feature inside the XBert app — Review module, Workflow, Capacity, Practice settings. Same data, same rules, persistent UI.
- Best for
- daily operations, team-shared visibility, persistent dashboards
- Lives in
- the XBert web app (browser)
- Connects via
- native integration with Xero, MYOB, QuickBooks Online, Xero Practice Manager
- What you get
- workflow templates, schedules, notifications, the Review module, audit history, role-based assignment
Where your assistant pulls ahead
XBert is built to surface the right information at the moment you're doing the work. Your assistant — running the XBert plugins — takes that further: arbitrary output formats, and everything else in your stack pulled into a single thread.
Any document, any format
XBert shows you the answer; your assistant shapes it into whatever you need. Board pack PDF, client email, Word brief, exported workpaper, plain summary — your assistant composes the artefact from live XBert data, then drops it back into your file system or the chat.
Your whole stack, one thread
Your assistant isn't just XBert. Through MCP it reaches your other connected systems — ledgers, mailbox, calendars, document store, and whatever else your firm runs. XBert is the accounting brain; your assistant brings the wider ecosystem into the same conversation.
Every slash command maps to a feature in XBert
How each published slash command lines up with screens in the product. The data, rules, and audit trail are the same either way.
| Plugin | What it does in chat | Where it lives in XBert |
|---|---|---|
| /anomaly-review | Ranked list of every anomaly XBert firing, verified (Word doc) | Review module → Exception items |
| /config-audit | XBert rule consistency across the book (Word doc) | Connect → XBert configuration |
| /workflow-review | Structural workflow audit (Word doc) | Practice → Workflow review report |
Why both surfaces?
Meet your team where they are
Some of your team lives in chat; some live in the app. XBert serves both without making either compromise.
Same audit trail, two entry points
Both surfaces write back to the same XBert audit log. A plugin run from chat is indistinguishable from an in-app run after the fact — same approvals, same artefacts, same compliance.
Open xbert.io to see the product
See the same workflows as the plugins, organised as a full practice product — with workflow templates, schedules, role-based assignment, and a persistent audit trail.