How to Use the Kaseya MCP in Claude Code

Q: Can I pipe Kaseya agent lists to other CLI tools using Claude Code?

Yes. You can command the agent to run listagents and output the results as raw JSON, allowing you to pipe the device list directly into local utilities.

Q: Can I review VSA 10 MCP workflows from the command line?

Yes. Running listworkflows returns a complete list of your active automation configurations, which the terminal-based MCP client formats for viewing.

Run headless Kaseya diagnostic pipelines and pipe VSA 10 agent telemetry directly into shell scripts using Claude Code.

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 Code

Create your Vinkius account to connect Kaseya to Claude Code 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 Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Headless Diagnostics and Terminal Pipelines

Executing `list_agents` lets you run complex endpoint diagnostics directly from your terminal session without opening a browser. This MCP Server lets you pipe the JSON output directly into local grep, jq, or custom bash scripts. When you need deep system details, pass the output to `get_system_info` to diagnose performance bottlenecks. You can execute these checks over SSH or embed them in automated cron jobs.

Build CI/CD Workflows for Claude Code

Checking your staging environment with `list_scripts` lets you verify administrative tasks before running them in production. The terminal agent uses this MCP Server to ensure your latest scripts match the current repository state. By calling `list_workflows`, the agent can programmatically verify that your automation policies are correctly assigned, preventing configuration drift across production environments. Keeping your infrastructure aligned becomes a background process instead of a manual chore.

Terminal-Based Alert Triage

Querying `list_alarms` lets you triage critical production alerts directly from your shell. Your agent fetches active system errors and filters them by severity using standard terminal utilities. Once an error is found, it uses `list_audit_logs` to correlate the alarm with recent administrative actions. This lets you immediately identify if a recent script run caused the system failure.

Setup guide

Set up Kaseya MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see kaseya-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Kaseya transactions." It will automatically discover and invoke the available Kaseya tools.

Terminal

claude mcp add --transport http kaseya-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Kaseya MCP

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

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "kaseya-mcp": {
      "type": "url",
      "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 Code

You add the server via the command line using the transport flag, which securely writes the API endpoint and keys to your local configuration file.

Yes. You can command the agent to run `list_agents` and output the results as raw JSON, allowing you to pipe the device list directly into local utilities.

The CLI agent manages request pacing when calling tools like `list_assets` to prevent API throttling during large infrastructure sweeps.

Yes. Running `list_workflows` returns a complete list of your active automation configurations, which the terminal-based MCP client formats for viewing.

Yes. The connection uses local transport protocols, ensuring your endpoint metrics and session logs never touch intermediate cloud relays.

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