cursor

Driving CEL from Cursor

This page shows how to drive CEL from Cursor.

Read docs/adapters-cel-agents.md first if you haven't.

Purpose

Cursor supports MCP servers from its composer / chat runtime, which makes CEL usable directly from the editor without any bespoke glue. In this setup:

• Cursor owns planning, tool selection, retries, and approval prompts.
• CEL exposes cel_see, cel_act, cel_perceive, cel_think over stdio MCP.
• You normally only need cel_see + cel_act from Cursor. Leave cel_think alone unless you explicitly want delegated autonomy.

Setup

1. Build CEL

cd /path/to/cellar
pnpm install && pnpm -r build

2. Register CEL as an MCP server

Cursor reads MCP servers from its global settings and/or project settings. The most reliable location is the global MCP config:

• macOS: ~/.cursor/mcp.json

TODO: verify with latest Cursor version — Cursor has iterated on MCP config paths. If ~/.cursor/mcp.json does not exist for you, check Cursor → Settings → MCP (the UI now exposes a server editor in recent builds). The stdio config block itself is stable across versions.

Add CEL:

{
  "mcpServers": {
    "cel": {
      "command": "node",
      "args": ["/absolute/path/to/cellar/mcp-server/dist/index.js"]
    }
  }
}

Or, if cellar is on your PATH:

{
  "mcpServers": {
    "cel": {
      "command": "cellar",
      "args": ["mcp"]
    }
  }
}

3. Confirm tools appear

Restart Cursor. Open Settings → MCP (or the equivalent panel). You should see cel listed with its four tools: cel_see, cel_act, cel_perceive, cel_think.

TODO: screenshot — Cursor Settings panel with CEL tools listed.

In the composer, enabling the CEL tools in the tool picker makes them callable from the current session.

4. Grant macOS Accessibility permission

The first call to cel_act that performs input will fail until the host process (Cursor, or the Node process Cursor spawns) has Accessibility permission. Grant it in System Settings → Privacy & Security → Accessibility and restart Cursor.