Skip to content

Cursor devops status mcp server devops_watch_stack

How to: Cursor devops status mcp server devops_watch_stack

client:Cursor transport:streamable-http tool:devops_watch_stack

Add devops status mcp server to Cursor

  1. 01

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

{
  "mcpServers": {
    "devops-status-mcp-server": {
      "url": "https://devops-status.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that devops status mcp server'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

devops status mcp server will not start until these are set, so devops_watch_stack never becomes available.

  • MCP_LOG_LEVEL
  • DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS
  • DEVOPS_STATUS_DISABLE_ACTIVE_PROBES

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.