Kaseya BMS MCP connector
The Kaseya BMS connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent read and update your Kaseya BMS accounts, contacts, locations, alerts, and attachments, with each person signed in as themselves and every action logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
329 tools
How to connect
How to connect Kaseya BMS to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Kaseya BMS once
-
Open Connections, choose Add connection, and pick Kaseya BMS.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Kaseya BMS API key. One person generates a token in Kaseya BMS and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Kaseya BMS MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Kaseya BMS MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Kaseya BMS MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Kaseya BMS to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Kaseya BMS through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Service desk
Review open alerts before the morning standup
Ask for the current Kaseya BMS alerts and who they are assigned to, so the desk knows what needs attention before anyone opens a queue.
-
Account management
Catch the client account up after a call
Update the Kaseya BMS CRM account with the new contact, address, or account type you just agreed on, without clicking through every field by hand.
-
Sales
Set up a new client account in minutes
Create the Kaseya BMS CRM account for a newly signed client with the right account type and account code already applied.
-
Operations
Find a site's details without hunting
Pull up a client location in Kaseya BMS by name or ID to confirm the address and site contacts before a technician heads out.
-
Technical services
Check what an agent procedure did overnight
Ask for the logs of a Kaseya BMS agent procedure and get a plain summary of what ran, where, and whether anything failed.
-
Finance
Confirm account codes before month-end billing
Look up Kaseya BMS account codes and account summaries so invoices go out against the right client record the first time.
Try asking
- “Summarize open alerts by account for this week.”
- “Which accounts opened the most tickets in March?”
- “List contacts at Northwind and their service locations.”
Compare
Elaichi vs Zapier MCP vs Composio for Kaseya BMS
All three can connect Kaseya BMS to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Kaseya BMS tools | Allow or restrict single Kaseya BMS tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Kaseya BMS call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Kaseya BMS tools for your AI agents
329 tools are ready to call through Elaichi's MCP endpoint the moment you connect Kaseya BMS, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Kaseya BMS gets you
6 screens from the product, each doing one job for your Kaseya BMS account.
The agent
Ask about tickets, get real answers.
Plain language questions run against live Kaseya BMS tickets, accounts and alerts.
- tickets
- accounts
- contacts
- alerts
Ask Elaichi to work across your apps.
Summarize open alerts by account for this week.
Which accounts opened the most tickets in March?
List contacts at Northwind and their service locations.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Kaseya BMS.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
329 Kaseya BMS tools ready to call.
Accounts, contacts, locations, alerts and agent procedures, with no custom code written.
- List all Kaseya BMS accountcodes lookups
- List all Kaseya BMS accounts lookups
- List all Kaseya BMS accounts summaries
- List all Kaseya BMS locations lookups
ElaichiToolsToolboxes
Every team gets its own toolbox.
Service desk, CRM and field teams each see only the Kaseya BMS tools they need.
- Service desk
- Sales
- Field operations
- Finance
ElaichiToolboxesShared connections
Teammates work tickets without seeing credentials.
Each Kaseya BMS connection shows who connected it and which teams share it.
- Service desk
- Sales EMEA
- Field operations
- Finance
ElaichiConnectionsAudit log
Answer who touched which account.
Every Kaseya BMS call lands append-only with time, person, action, type and resource.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest ships.
Six steps fetch Kaseya BMS tickets, group them, draft, wait for approval, post back.
Kaseya BMS digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tickets
Kaseya BMS
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Kaseya BMS
Queued
Collections and dashboards
Kaseya BMS health, counted not asked.
Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.
Kaseya BMS health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Accounts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Service desk 34%
Sales EMEA 27%
Field operations 21%
Finance 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Kaseya BMS to Claude?
Connect Kaseya BMS in Elaichi first, which means pasting in a Kaseya BMS API key when prompted. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when Claude asks and your Kaseya BMS accounts, contacts, locations, and alerts are available.
Does Kaseya BMS work with ChatGPT and Cursor as well as Claude?
Yes. Once Kaseya BMS is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Kaseya BMS once and every client you use picks it up.
What can an AI agent actually do with my Kaseya BMS data?
An agent can look up Kaseya BMS accounts, contacts, locations, and account codes, list current alerts and who they are assigned to, create or update a CRM account, read agent procedure logs, and manage attachments. Because Kaseya BMS has hundreds of actions, the agent searches for the right one as you ask, so short concrete requests like "show me open alerts for Acme" work better than long paragraphs.
Does connecting Kaseya BMS give the AI access to every client and account?
No. Access follows the person who signed in, so the AI sees the Kaseya BMS accounts, locations, and alerts that person can already see and nothing more. Elaichi can narrow that further by restricting which actions are allowed, but it can never widen what Kaseya BMS itself permits.
Can I stop an agent from deleting or changing things in Kaseya BMS?
Yes. Restrictions in Elaichi work per action, so you can allow reading Kaseya BMS accounts and alerts while blocking updates or attachment deletion entirely. A blocked action is never advertised to Claude, ChatGPT, or Cursor, so no prompt, accidental or otherwise, can reach it.
What happens to a Kaseya BMS connection when someone leaves?
Offboarding a person in Elaichi ends their access to Kaseya BMS through every AI client at once. A shared Kaseya BMS connection keeps working for everyone else on the team. If you ever want to remove Kaseya BMS completely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Does the Kaseya BMS MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Kaseya BMS is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Kaseya BMS?
Yes. Both let Claude, ChatGPT or Cursor use Kaseya BMS. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Kaseya BMS call.
How is Elaichi different from Composio for Kaseya BMS?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Kaseya BMS: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Kaseya BMS in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.