How to Use the Kaseya MCP in Cursor

Q: How do I configure the Kaseya MCP Server for Cursor?

Create an mcp.json file in your project root or global .cursor directory. Add the server command or remote URL, then enable Agent mode in your chat panel.

Q: Can Cursor modify my Kaseya machine groups?

No. The tools are strictly read-only. Cursor uses listgroups to read your segmentation, but it cannot create or delete any machine groups.

Q: Will this MCP Server pull my entire Kaseya asset list at once?

That depends on your prompt. The listassets tool returns large datasets, so it's best to ask the AI to filter the results by specific organizations or tags.

Inject live Kaseya VSA 10 data straight into your Cursor workspace. Write automation scripts with real agent details and system info.

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 Cursor

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Query live agents in Cursor

The `list_agents` tool gives Cursor direct access to your managed devices. When you write custom monitoring scripts, the AI pulls real machine statuses instead of guessing at variable names. You build logic around actual infrastructure. You can drill down further while coding. The AI triggers `get_agent_details` to pull specific hardware profiles or `get_system_info` for VSA 10 environment variables. Your code gets written against the exact systems it will eventually manage.

Build tools around Kaseya alarms

The `list_alarms` tool feeds active system alerts directly into your editor context. If you are writing an incident response integration, Cursor can see exactly how the alerts are structured. Stop relying on outdated API documentation. The AI reads the live schema from your actual warnings. It writes parsing logic that works on the first try because it already saw the real data.

Audit scripts with this MCP Server

The `list_scripts` tool lets Cursor read the agent scripts currently deployed in your environment. You can check existing automation before writing new code to avoid duplicating effort. The same applies to broader automation. Cursor hits `list_workflows` to map out your current operational routines. You can also pull `list_audit_logs` to ensure your new scripts comply with recent administrative patterns.

Setup guide

Set up Kaseya MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Kaseya MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Kaseya transactions." If the MCP tools are loaded correctly, Cursor will call the Kaseya tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/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 Cursor

Create an `mcp.json` file in your project root or global `.cursor` directory. Add the server command or remote URL, then enable Agent mode in your chat panel.

No. The tools are strictly read-only. Cursor uses `list_groups` to read your segmentation, but it cannot create or delete any machine groups.

That depends on your prompt. The `list_assets` tool returns large datasets, so it's best to ask the AI to filter the results by specific organizations or tags.

Cursor executes tools exactly as you instruct it. If you ask it to repeatedly call `get_agent_details` in a loop, it will hit the VSA 10 rate limits. Be specific in your prompts.

Cursor routes requests through our ephemeral V8 Isolate Sandbox. When the AI calls `list_organizations`, the server fetches the tenant list and immediately dumps the memory. Nothing persists after the connection closes.

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