Skip to content

Cursor monity.ai delete_monitor

How to: Cursor monity.ai delete_monitor

client:Cursor transport:streamable-http tool:delete_monitor

Add monity.ai to Cursor

  1. 01

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

{
  "mcpServers": {
    "monity": {
      "url": "https://api.monity.ai/plugins/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that monity.ai'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

monity.ai will not start until these are set, so delete_monitor never becomes available.

  • MONITY_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 8 November 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.