Claude Desktop (local server)
Run the Helipod MCP server locally in the Claude desktop app with an API key.
This setup follows Claude Desktop's local MCP server configuration.
Requirements
- Claude Desktop (macOS or Windows), Node.js 18 or newer.
- A Helipod API key, see Get a key.
Add the server
In Claude Desktop open Settings → Developer → Edit Config. That opens claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"helipod": {
"command": "npx",
"args": ["-y", "helipod-mcp"],
"env": {
"HELIPOD_API_KEY": "hel_your_key",
"HELIPOD_EMAIL_API_KEY": "your_email_key"
}
}
}
}Claude Desktop does not read your shell's environment variables, so the key goes in the file. Save, then quit Claude Desktop completely and start it again.
The easier way is the hosted server with sign-in, which needs no key and no Node.js: see Claude.ai and Claude Desktop. Use this page if you prefer a local server with an API key.
Check it works
- In a new chat, open the tools menu (the slider / tools icon): helipod is listed with its tools.
- Ask: "List my Helipod projects." Claude asks for permission before each tool.
Skills
Claude Desktop does not read SKILL.md folders from disk. The server's own instructions already tell Claude to show prices and confirm destructive actions. If your plan supports custom skills, you can upload the folders from skills/ as zip files in Settings → Capabilities.
Troubleshooting
Open Settings → Developer: the server's status and log are shown there. Check that the JSON is valid (no trailing commas).
Claude Desktop starts without your shell's PATH, so Node.js from nvm, fnm or Homebrew may be missing. Use the full path from which npx as command, for example "/opt/homebrew/bin/npx".
Use "command": "cmd" with "args": ["/c", "npx", "-y", "helipod-mcp"].