ACF
acfstandard.io
Developer docs
FR
Integration

Cursor

Add acf-mcp to Cursor so its agent can call ACF governance tools directly inside your IDE.

iNote
Cursor is a VS Code-based IDE with a built-in agent. It supports MCP over stdio and HTTP, and accepts either a global (~/.cursor/mcp.json) or per-project (.cursor/mcp.json at the repo root) configuration.

Prerequisites

  • Node.js ≥ 18 (check with node --version)
  • Cursor — cursor.com (macOS, Windows, Linux)

Install

  1. Open MCP settings

    Two options: GUI (Cursor → Settings → Features → MCP Servers → Add new server) or edit the JSON file directly.

  2. Paste the configuration

    Edit ~/.cursor/mcp.json (create the file if missing). Applies to all projects.

    ~/.cursor/mcp.jsonjson
    {
  "mcpServers": {
    "acf": {
      "command": "npx",
      "args": ["-y", "acf-mcp"]
    }
  }
}

  3. Enable the server in settings

    Settings → Features → MCP Servers: toggle acf to ON. Cursor spawns the process and lists the detected tools.

  4. Reload Cursor

    Cmd/Ctrl+Shift+P → “Developer: Reload Window” is enough. No need to quit the app.

Verify

  1. Check the tool list

    Settings → MCP Servers: the acf entry should show a green dot and the detected tool count (13 expected).

  2. Test prompt in the agent chat

    Open the agent chat (Cmd/Ctrl+L), switch to Agent mode, then type: “Use acf.advisor to assess governance of a B2B lead-qualification agent”.

    The agent must call the tool and return a signed reply (doctrine_hash, doctrine_signature, generated_at).

Advanced config

HTTP transport

Cursor accepts a remote HTTP endpoint. Useful to share acf-mcp server-side or enforce a per-user API key.

~/.cursor/mcp.jsonjson
{
  "mcpServers": {
    "acf": {
      "url": "https://your-acf-mcp.example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ACF_API_KEY"
      }
    }
  }
}

See /docs/authentication for deploying acf-mcp over HTTP with API-key auth.

Auto-approval

Cursor asks for approval on every tool call by default. Settings → Features → MCP → check the acf tools you want to auto-approve. All ACF tools are deterministic and side-effect-free: no risk of write operations.

Troubleshooting

  • Red dot next to acf. Click it to open server logs. Most common cause: Node not found or malformed JSON.
  • Agent does not list MCP tools. Check you are in Agent mode (not Chat). Chat mode ignores MCP tools.
  • Conflict with project .cursor/mcp.json. Project config overrides global for same-named servers. Rename the entry (acf-local, acf-prod) if you need both.
  • Cursor on Windows cannot find npx. Replace npx with npx.cmd in the command key.
  • Startup timeout. First npx = package download. Wait ~10 s, reload window. Subsequent runs are instant (npx cache).