Cline, Roo Code, Kilo Code

These VS Code extensions keep their own MCP settings, separate from VS Code's mcp.json. This setup follows their MCP settings format.

RequirementsCopy Anchor Link

• The extension in VS Code, Node.js 18 or newer for the local server.
• A Helipod API key, see Get a key.

Add the serverCopy Anchor Link

Open the extension's MCP Servers view and choose Configure MCP Servers (Cline) or Edit Global MCP (Roo Code, Kilo Code). Add:

{
  "mcpServers": {
    "helipod": {
      "command": "npx",
      "args": ["-y", "helipod-mcp"],
      "env": { "HELIPOD_API_KEY": "hel_your_key" },
      "disabled": false
    }
  }
}

Roo Code and Kilo Code can also read a project file (.roo/mcp.json, .kilocode/mcp.json) with the same content. Do not commit a real key.

Each server has an auto-approve list (autoApprove / alwaysAllow). Put only read-only tools there, for example list_projects, get_service, get_deployment_logs; never tools that cost money or delete things.

Add the skillsCopy Anchor Link

npx skills add helipodapp/mcp -g -a cline     # or: -a roo, -a kilo

Check it worksCopy Anchor Link

• The MCP Servers view shows helipod with a green status and its tools.
• Ask: "List my Helipod projects."

To run these extensions on Helipod AI models, see Coding tools → Cline, Roo Code and Kilo Code.