Connect BUZ to Claude

For any BUZ user · ~4 min read

BUZ has an official connector for Claude. Once it’s connected, you can ask about your own BUZ data in plain English — “how many leads came in last week?”, “what’s on the install schedule tomorrow?” — instead of running a report.

You see only what you'd see in BUZ

The connector signs you in as you. It can only reach the organisation you pick when you connect, and only the data your BUZ permissions already allow. It is not a way to see anyone else’s organisation.

Connect it

You’ll need a Claude account and your normal BUZ login.

1. In Claude, open Settings → Connectors.

2. Choose Add custom connector.

3. Give it a name — BUZ MCP is the obvious one — and enter the connector URL:

   https://mcp.buzmanager.com

   Leave Advanced settings alone. The OAuth client ID and secret are optional and BUZ doesn’t need them, and Individual sign-in is the connection method you want — each person signs in to BUZ as themselves.

4. Select Add. Claude opens the BUZ Authorisation page. Log in with your usual BUZ credentials if you’re not already signed in.

5. Pick your organisation from the dropdown and choose Allow Access.

6. You’re returned to Claude with BUZ listed as a connector.

Test it by asking Claude: “Using BUZ, who am I and which organisation am I connected to?” It should answer with your name and the organisation you picked.

Figure 1 — Claude’s Add custom connector dialog. Give it a name and the BUZ connector URL. The OAuth Client ID and Secret under Advanced settings are optional and BUZ doesn’t use them — leave them blank. Individual sign-in is the connection method you want, so each person signs in to BUZ as themselves.

Figure 2 — the BUZ Authorisation screen. Pick the organisation you want Claude to work with, then Allow Access. This is the choice that fixes which organisation the connector sees — to change it later you disconnect and add the connector again.

What you can ask

You don’t need to learn any commands — ask in plain English and mention BUZ. Some examples:

Leads and sales

• “How many leads did we get last month, and how many converted?”
• “Show me open leads for the Northern branch.”
• “Which sales rep wrote the most business this quarter?”
• “Book a follow-up appointment for the Henderson lead next Tuesday morning.”

Customers

• “Find the customer with the email address jo@example.com.”
• “What’s the recent activity on the Bayside Blinds account?”
• “Log a call activity against this customer saying I’ve quoted them.”

Orders and production

• “What orders are in production right now?”
• “Show me work in progress.”
• “Move order 10432 to the next status.”

Scheduling and installs

• “What’s on the dispatch schedule for Thursday?”
• “Which jobs are booked for install next week?”

Settings

• “List our branches and tax rates.”
• “Add a new branch called Western Suburbs.”

Ask it to check before it changes anything

Claude can create and update records, not just read them. If you’d rather it always confirmed first, just say so — “always show me what you’re about to change in BUZ and wait for me to say yes” — at the start of the conversation.

Control what Claude can do

Open the connector in Settings → Connectors → BUZ MCP and you get Tool permissions — a list of everything Claude can do in BUZ, split into read tools and write/delete tools. Each one can be set to:

• Always allow — Claude uses it without asking.
• Ask — Claude checks with you first.
• Deny — Claude can’t use it at all.

You only see tools your BUZ permissions already allow, so this narrows what Claude can do — it can never widen it.

A sensible starting point

Leave the read tools on Always allow and set the write/delete group to Ask. You get quick answers to questions, and anything that changes your data pauses for a yes. Tighten individual tools from there if you want.

Disconnect is on the same screen when you want to remove the connector entirely.

One organisation per connection

You choose an organisation when you connect, and the connector stays on it. To work with a different organisation, disconnect the connector in Claude and add it again, choosing the other organisation.

Good to know

Tip

• Your permissions apply. If you can’t see purchasing in BUZ, Claude can’t see it for you either.
• Changes are real. Anything Claude creates or updates happens in your live BUZ data, recorded against your user — the same as if you’d typed it in yourself.
• Check the numbers that matter. Claude is good at pulling and summarising, but for anything you’d act on financially, confirm against the matching report.
• It works in Claude apps and on claude.ai — the connector follows your Claude account.

Troubleshooting

What you see	What to do
Sign-in loop, or “not authorised”	Your BUZ session may have expired. Remove the connector in Claude and add it again.
Wrong organisation’s data	The organisation is fixed when you connect. Remove the connector and re-add it, picking the right one.
“I don’t have access to that”	Your BUZ user group doesn’t include that area. See Groups & permissions.
Nothing comes back, or errors on every question	Check you can sign in to BUZ normally in a browser first.

See also

• Integrations overview
• Webhooks (developer API) — for building custom automation instead.