VS Code (GitHub Copilot)

Connect Causely to GitHub Copilot in VS Code to query root causes and service health from Copilot Chat.

Prerequisites

• Active Causely account
• VS Code with the GitHub Copilot extension (version 0.22+ for MCP support)

Configuration

Create or update .vscode/mcp.json in your workspace:

{
  "servers": {
    "causely": {
      "type": "http",
      "url": "https://api.causely.app/mcp"
    }
  }
}

note

VS Code Copilot uses servers as the top-level key, not mcpServers. Using mcpServers silently fails, the server simply won't appear.

Config file location

Scope	Path
Workspace	.vscode/mcp.json at the repository root
User	Command Palette → MCP: Open User Configuration

Restart

After saving the config, open the Command Palette and run MCP: List Servers to confirm causely appears. Copilot Chat picks up the server on the next conversation turn, no full restart required.

tip

Skills are not yet supported for VS Code Copilot. You'll interact with the Causely MCP server directly; the example prompts in the Key Workflows section still work, but tool selection is handled by GitHub Copilot's agent rather than a Causely skill router.

Try It Now

• "List my clusters."
• "Are there any active symptoms right now?"
• "What services are currently degraded?"

Known Gotcha

If your organization uses GitHub Copilot Business or Enterprise, an admin may need to allow MCP servers in the Copilot policy settings before user-configured servers can connect. See Advanced Authentication for adding machine credentials via headers or VS Code inputs.