Skip to content

VS Code devops status mcp server devops_status_check

How to: VS Code devops status mcp server devops_status_check

client:VS Code transport:streamable-http tool:devops_status_check

Add devops status mcp server to VS Code

  1. 01

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

{
  "servers": {
    "devops-status-mcp-server": {
      "type": "http",
      "url": "https://devops-status.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something devops_status_check does. VS Code lists the server's tools on connect and calls devops_status_check 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.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

devops status mcp server will not start until these are set, so devops_status_check 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.