Onyx One speaks MCP, the open connector standard the AI industry is converging on. That means you drive your business from the Claude or ChatGPT you already pay for, rather than learning a chatbot we built.
The setup
- In Claude, add a custom connector and paste one URL: onyx1.app/api/mcp
- You are bounced to an Onyx One sign-in and asked to approve the connection. There is no token to copy or paste.
- That is it. Ask what is on today, and it will tell you.
Claude Desktop and Cursor work as well, using a generated connection token. Bringing your own AI is included from the Pro plan, and every trial runs the full Pro feature set.
What it can actually do
There are 63 tools available to your AI, covering the working day: what is on today, who is on site, drafting a quote, logging time and parts, raising a variation, reporting an incident, requesting leave, approving a timesheet, marking an invoice paid.
What it cannot do, and why that matters
The boundary is your role, and it is enforced in the database rather than requested in a prompt. A tech's AI cannot read a price or delete a protected record, even if it is asked to, and even if someone tries to talk it into it.
- New connections start with read access plus safe writes. Money moves and anything customer-facing are opt-in, per connection.
- Sensitive writes return a preview and a short-lived confirmation token bound to that exact request, so a token for a $10 invoice cannot be replayed for a $10,000 one.
- Every tool call and confirmation lands in the audit trail, and writes are idempotent, so a retry never doubles up.
- Onyx One recomputes every total itself. Your AI narrates the numbers, it never invents them.
This is worth checking whenever you connect any AI to a business system: ask whether the connector runs as you, or as an administrator. If it needs admin rights to work, then everyone using it has admin rights.