Skip to content

Cursor checklist run_start

How to: Cursor checklist run_start

client:Cursor transport:streamable-http tool:run_start

Add checklist to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "checklist": {
      "url": "https://mcp.zovo.one/mcp/checklist"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something run_start does. Cursor lists the server's tools on connect and calls run_start itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that checklist's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

checklist will not start until these are set, so run_start never becomes available.

  • MCP_LICENSE_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.