Connect Gemini to Monita

Gemini CLI and Gemini Code Assist support MCP servers through the mcpServers setting. Once added, Monita’s tools are available in every session.

Gemini CLI

1. Create an API key at Settings → API keys.

2. Add Monita to ~/.gemini/settings.json (create the file if it doesn’t exist):

   {
     "mcpServers": {
       "monita": {
         "httpUrl": "https://api.monita.ai/mcp",
         "headers": { "Authorization": "Bearer ak_your_key_here" }
       }
     }
   }

3. Start gemini and confirm the connection with /mcp — Monita’s tools should be listed.

4. Try: “What are my worst Monita issues this week?”

Project-level setup works the same way in .gemini/settings.json at the repo root — useful when a team repo should always carry Monita access. Keep keys out of version control: reference an environment variable ("Authorization": "Bearer $MONITA_API_KEY") rather than committing the key.

Gemini Code Assist

Gemini Code Assist in VS Code reads the same mcpServers configuration as Gemini CLI — complete the steps above and Monita is available in the Code Assist chat too.

What to try first

• “Use Monita to check whether our GA4 volumes are anomalous this week.”
• “List open compliance issues and summarize what changed since Friday.”
• “Which vendors fire on our checkout pages without a policy verdict?”

The full tool list is on the MCP server page. Using a different client? The general MCP guide covers any MCP-capable assistant.