Can Cursor call Automation Skill Builder skills via MCP?

Yes. Run ASB locally, enable Communication / MCP in Settings, then point Cursor MCP config at the local SSE endpoint (default http://127.0.0.1:8800/mcp/sse). Skill execution stays on your machine.

Does Cursor MCP require cloud runtime for ASB skills?

No. ASB skill invocation and quota checks run on-device. Cursor only sends tool calls to your local MCP server.

All posts Home

Product blog · Recipe

Call local ASB skills from Cursor via MCP

A concrete recipe: run Automation Skill Builder on your machine, expose packaged skills as MCP tools, and invoke them from Cursor — without moving desktop execution to the cloud.

July 25, 2026 · Updated July 25, 2026

Conclusion first

Yes — Cursor can call local Automation Skill Builder (ASB) skills through MCP. ASB stays the local control plane; Cursor is the assistant client. Runtime skill calls and license quota checks happen on your host, not on a vendor desktop cloud.

Default endpoint: http://127.0.0.1:8800/mcp/sse (SSE). Confirm the exact URL and any auth header in Settings → Communication / MCP — UI values win over this article if they differ.

Prerequisites

ASB desktop app running; Control Panel opens (often http://127.0.0.1:8800).
At least one packaged skill (or use built-in tools while designing).
Cursor installed with MCP support enabled.
Optional: service secret / token if you secured the MCP endpoint in Settings.

Steps

1. Enable MCP in ASB

Open Settings → Communication / MCP. Complete the on-screen steps for your client. Review tool visibility so Cursor only sees tools you intend to expose. Restart ASB if the UI asks.

2. Point Cursor at the local MCP server

Add an MCP server entry in Cursor (project or global MCP settings). Example SSE shape — replace URL/headers with what ASB Settings shows:

{
  "mcpServers": {
    "automation-skill-builder": {
      "url": "http://127.0.0.1:8800/mcp/sse"
    }
  }
}

If your Settings page documents a bearer token, add the Authorization header your client expects. Do not paste secrets into public repos.

3. Verify tools, then call a skill

Restart Cursor (or reload MCP) if tools do not appear.
Ask Cursor to list available ASB tools / skills.
Run a low-risk skill once and confirm the run appears in ASB (Usage / run history).

What stays local

Skill execution and quota enforcement on the host.
Desktop / browser / file / API actions driven by ASB — not by a remote operator sandbox.
License file model: paid tiers refresh license.json periodically; not a per-call cloud entitlement API.

FAQ

Is MCP required to use ASB?

No. Core authoring and runs work via the web UI and HTTP API. MCP is optional when you want Cursor (or other assistants) to call packaged capabilities.

Cursor vs VS Code?

Same local ASB server. VS Code often uses an mcp.servers SSE entry; Cursor uses its MCP config UI/file. See also MCP everywhere and third-party MCP patterns.

Connection fails?

Confirm ASB is running, port matches Settings, firewall allows loopback, and tool visibility includes what you need. Manual: §12.3 AI cannot connect.

Download ASB Open manual §10