How to Use the Kaseya MCP in Claude

Q: How do I install the Kaseya MCP Server in Claude Desktop?

You have two options. Add the server command to your claudedesktopconfig.json file and restart, or paste the remote URL into the Integrations tab on claude.ai. Both methods give you instant access to your VSA 10 environment.

Q: Can Claude Desktop run Kaseya automation scripts directly?

No. The integration reads data using tools like listscripts and listworkflows. It shows you what automation exists, but it cannot trigger or modify those routines.

Q: Does the Kaseya integration for Claude Desktop support multiple organizations?

Yes. The listorganizations tool pulls every tenant your credentials can access. You can ask Claude to filter alarms or agents for a specific client group.

Manage your IT infrastructure directly from Claude Desktop. Pull active alarms, check agent details, and audit systems without leaving chat.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Kaseya MCP to Claude Desktop

Create your Vinkius account to connect Kaseya to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Kaseya with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Audit IT infrastructure via Claude Desktop

The `list_agents` tool pulls your exact device availability and status into the chat interface. Ask Claude for offline machines, and it queries Kaseya VSA 10 directly to build that list. You skip switching tabs or logging into a separate dashboard. Need deeper context on a specific machine? Your agent runs `get_agent_details` to grab the exact specs and current state. Combine this with `get_system_info` to map out your entire VSA 10 environment right from your local desktop or the web app.

Monitor alarms and compliance

The `list_alarms` tool feeds active system warnings straight to your AI client. If a server drops or a drive fills up, you see the alert data immediately. You don't wait for an email notification. Tracking who did what is just as fast. Claude uses `list_audit_logs` to pull recent administrative actions. You get a clear timeline of system changes, making compliance checks a simple conversation instead of a manual report generation task.

Map organizations and assets

The `list_organizations` tool lets this MCP Server fetch your exact tenant structure. You can map out client environments and follow up with `list_groups` to see how machines are segmented. When you need hardware specifics, `list_assets` grabs the managed asset records. You can even check available automation routines using `list_scripts` and `list_workflows` to see exactly what maintenance options exist for those assets.

Setup guide

Set up Kaseya MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Kaseya MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Kaseya MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under kaseya-mcp.

json

{
  "mcpServers": {
    "kaseya-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Kaseya. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Kaseya now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Kaseya MCP in Claude Desktop

You have two options. Add the server command to your `claude_desktop_config.json` file and restart, or paste the remote URL into the Integrations tab on claude.ai. Both methods give you instant access to your VSA 10 environment.

No. The integration reads data using tools like `list_scripts` and `list_workflows`. It shows you what automation exists, but it cannot trigger or modify those routines.

Your authentication token might lack the right permissions. The `get_agent_details` tool requires valid VSA 10 credentials passed through the connection. Check your config file or connector settings.

Yes. The `list_organizations` tool pulls every tenant your credentials can access. You can ask Claude to filter alarms or agents for a specific client group.

Vinkius isolates your data using a zero-trust V8 sandbox. When Claude requests records via `list_audit_logs`, the ephemeral environment processes the request and destroys itself immediately. Your administrative history never touches persistent storage.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript