Gemini CLI
Add the Helipod MCP server and skills to Gemini CLI, local or hosted.
Tested with Gemini CLI 0.64: local and hosted server, key passed from the environment, skills listed by gemini skills list.
Requirements
- Gemini CLI, Node.js 18 or newer.
HELIPOD_API_KEYin your environment, see Get a key.
Add the server
Edit ~/.gemini/settings.json (all projects) or .gemini/settings.json in a project:
{
"mcpServers": {
"helipod": { "httpUrl": "https://api.helipod.io/mcp" }
}
}Start Gemini CLI and run /mcp auth helipod. Sign in to Helipod in the browser, choose the products and reach, and Allow.
If settings.json already has other settings, add mcpServers next to them.
Gemini CLI starts MCP servers only in trusted folders, including servers from your user settings. Trust the folder when Gemini asks, or gemini mcp list shows the server as disabled.
Add the skills
npx skills add helipodapp/mcp -g -a gemini-cligemini skills list then shows the six helipod skills.
Check it works
gemini mcp listshows✓ helipod … Connected.- Inside Gemini CLI,
/mcplists the Helipod tools. - Ask: "List my Helipod projects."
Gemini CLI asks before each tool call. Do not set "trust": true on the server: that skips the confirmation for every tool, including paid and destructive ones.
Troubleshooting
Trust the folder (Gemini asks when you start it there), then run gemini mcp list again.
The Authorization header is missing or empty. Check that HELIPOD_API_KEY is set in the terminal you start Gemini from.
Gemini CLI uses Google's models only; it cannot run on Helipod AI Gateway models.