SERVER

Kaseya BMS

Rank #9,620

io.github.WYRE-AI/kaseya-bms-mcp

MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.

11 versions

by wyre-technology (60 servers)View repository ↗

First listed

May 1, 2026

Last publish date

Oct 14, 2026

PURPOSE

What you can do with Kaseya BMS

Kaseya BMS is a Model Context Protocol (MCP) server published by wyre-technology. It ranks #9,620 of 144,396 active servers on MCP Toplist. Kaseya BMS is listed across 3 registries — Official MCP, PulseMCP and Glama, with 11 tracked versions. It was first listed on May 1, 2026 and most recently updated on Oct 14, 2026.

Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. The repository README is the authority on what it does.

CAPABILITIES AND LIMITATIONS

What Kaseya BMS can and cannot do

Not verifiedMCP Toplist has not catalogued this server's tools or limitations. The repository README lists them.

REQUIREMENTS

What you need before using Kaseya BMS

DeclaredNo credentialsNo credentials declared

The registry listing declares no required environment variables or authentication. This is declared metadata, not a verified install — the repository README is the authority.

Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.

Declared in the registry install config

KASEYA_BMS_TENANT_SUBDOMAIN · required
KASEYA_BMS_API_TOKEN · optional
KASEYA_BMS_K1_TOKEN · optional
MCP_TRANSPORT · optional
AUTH_MODE · optional
LOG_LEVEL · optional

INSTALLATION AND FIRST TASK

Connect Kaseya BMS and confirm it works

Docker image

claude mcp add kaseya-bms-mcp -e "KASEYA_BMS_TENANT_SUBDOMAIN=<your KASEYA_BMS_TENANT_SUBDOMAIN>" -e "KASEYA_BMS_API_TOKEN=<your KASEYA_BMS_API_TOKEN>" -e "KASEYA_BMS_K1_TOKEN=<your KASEYA_BMS_K1_TOKEN>" -e "MCP_TRANSPORT=<your MCP_TRANSPORT>" -e "AUTH_MODE=<your AUTH_MODE>" -e "LOG_LEVEL=<your LOG_LEVEL>" -- docker run -i --rm ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6

Replace each placeholder with your own value before saving.

Docker image

[mcp_servers.kaseya-bms-mcp]
command = "docker"
args = ["run", "-i", "--rm", "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6"]

[mcp_servers.kaseya-bms-mcp.env]
KASEYA_BMS_TENANT_SUBDOMAIN = "<your KASEYA_BMS_TENANT_SUBDOMAIN>"
KASEYA_BMS_API_TOKEN = "<your KASEYA_BMS_API_TOKEN>"
KASEYA_BMS_K1_TOKEN = "<your KASEYA_BMS_K1_TOKEN>"
MCP_TRANSPORT = "<your MCP_TRANSPORT>"
AUTH_MODE = "<your AUTH_MODE>"
LOG_LEVEL = "<your LOG_LEVEL>"

Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.

Docker image

{
  "mcpServers": {
    "kaseya-bms-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6"
      ],
      "env": {
        "KASEYA_BMS_TENANT_SUBDOMAIN": "<your KASEYA_BMS_TENANT_SUBDOMAIN>",
        "KASEYA_BMS_API_TOKEN": "<your KASEYA_BMS_API_TOKEN>",
        "KASEYA_BMS_K1_TOKEN": "<your KASEYA_BMS_K1_TOKEN>",
        "MCP_TRANSPORT": "<your MCP_TRANSPORT>",
        "AUTH_MODE": "<your AUTH_MODE>",
        "LOG_LEVEL": "<your LOG_LEVEL>"
      }
    }
  }
}

Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.

Docker image

{
  "mcpServers": {
    "kaseya-bms-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6"
      ],
      "env": {
        "KASEYA_BMS_TENANT_SUBDOMAIN": "<your KASEYA_BMS_TENANT_SUBDOMAIN>",
        "KASEYA_BMS_API_TOKEN": "<your KASEYA_BMS_API_TOKEN>",
        "KASEYA_BMS_K1_TOKEN": "<your KASEYA_BMS_K1_TOKEN>",
        "MCP_TRANSPORT": "<your MCP_TRANSPORT>",
        "AUTH_MODE": "<your AUTH_MODE>",
        "LOG_LEVEL": "<your LOG_LEVEL>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.

Docker image

{
  "servers": {
    "kaseya-bms-mcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6"
      ],
      "env": {
        "KASEYA_BMS_TENANT_SUBDOMAIN": "<your KASEYA_BMS_TENANT_SUBDOMAIN>",
        "KASEYA_BMS_API_TOKEN": "<your KASEYA_BMS_API_TOKEN>",
        "KASEYA_BMS_K1_TOKEN": "<your KASEYA_BMS_K1_TOKEN>",
        "MCP_TRANSPORT": "<your MCP_TRANSPORT>",
        "AUTH_MODE": "<your AUTH_MODE>",
        "LOG_LEVEL": "<your LOG_LEVEL>"
      }
    }
  }
}

Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.

Docker image

{
  "mcpServers": {
    "kaseya-bms-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6"
      ],
      "env": {
        "KASEYA_BMS_TENANT_SUBDOMAIN": "<your KASEYA_BMS_TENANT_SUBDOMAIN>",
        "KASEYA_BMS_API_TOKEN": "<your KASEYA_BMS_API_TOKEN>",
        "KASEYA_BMS_K1_TOKEN": "<your KASEYA_BMS_K1_TOKEN>",
        "MCP_TRANSPORT": "<your MCP_TRANSPORT>",
        "AUTH_MODE": "<your AUTH_MODE>",
        "LOG_LEVEL": "<your LOG_LEVEL>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.

Docker image

{
  "mcpServers": {
    "kaseya-bms-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6"
      ],
      "env": {
        "KASEYA_BMS_TENANT_SUBDOMAIN": "<your KASEYA_BMS_TENANT_SUBDOMAIN>",
        "KASEYA_BMS_API_TOKEN": "<your KASEYA_BMS_API_TOKEN>",
        "KASEYA_BMS_K1_TOKEN": "<your KASEYA_BMS_K1_TOKEN>",
        "MCP_TRANSPORT": "<your MCP_TRANSPORT>",
        "AUTH_MODE": "<your AUTH_MODE>",
        "LOG_LEVEL": "<your LOG_LEVEL>"
      }
    }
  }
}

Replace each placeholder with your own value before saving.

First successful task

After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.

ALTERNATIVES

When to choose another server

Other servers by wyre-technology

View all wyre-technology servers →

No task-specific alternatives are catalogued for Kaseya BMSyet; the list above is its publisher's other servers.

MAINTENANCE AND EVIDENCE

What changed, and when this was checked

First listed: May 1, 2026
Latest version published: Oct 14, 2026
Version history: 11 versions tracked (below)
Requirements evidence: Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.
Profile checked: Not yet — purpose, capabilities and requirements above come from registry data only
Ranking data as of: Oct 16, 2026

Registry sightings

Official MCP ↗listed since May 1, 2026 · still listed
PulseMCP ↗listed since May 22, 2026 · still listed
Glama ↗listed since Jun 4, 2026 · delisted, last seen Aug 26, 2026
Official MCP ↗listed since Aug 27, 2026 · still listed
Glama ↗listed since Sep 4, 2026 · still listed

Do you maintain Kaseya BMS? to correct or enrich this profile.

VERSIONS

Available versions (11)

Version	Published
1.1.6	Oct 14, 2026
1.1.5	Aug 26, 2026
1.1.4	Aug 20, 2026
1.1.3	Aug 13, 2026
1.1.2	Aug 10, 2026
1.1.1	Jul 29, 2026
1.1.0	Jul 17, 2026
1.0.7	Jul 13, 2026
1.0.6	May 30, 2026
1.0.1	May 21, 2026
1.0.0	May 1, 2026

STANDING

#9,620of 144,396 active serversTop 10%

Ranks ahead of 134,776 of 144,396 servers on MCP Toplist.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/io.github.WYRE-AI%2Fkaseya-bms-mcp.svg)](https://mcptoplist.com/server/io.github.WYRE-AI%2Fkaseya-bms-mcp)

HTML

<a href="https://mcptoplist.com/server/io.github.WYRE-AI%2Fkaseya-bms-mcp"><img src="https://mcptoplist.com/badge/io.github.WYRE-AI%2Fkaseya-bms-mcp.svg" alt="MCP Toplist: Top 10% of 144,396" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

FAQ

Frequently asked questions

Who maintains Kaseya BMS?: Kaseya BMS is maintained by wyre-technology, which publishes 60 MCP servers (872 total versions) tracked on MCP Toplist.
Is Kaseya BMS listed on the Official MCP Registry?: Yes — Kaseya BMS is listed on the Official MCP Registry, alongside PulseMCP and Glama.
How many versions does Kaseya BMS have?: MCP Toplist tracks 11 versions of Kaseya BMS, most recently published on Oct 14, 2026.
Where can I find the source code for Kaseya BMS?: The source code for Kaseya BMS is hosted at github.com/wyre-technology/kaseya-bms-mcp.

Used in projects

Do you run this server?

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Official MCP Servers GitHub MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers