Gemini

Google Gemini supports MCP through Gemini CLI, letting you use Toolcog for API operations from your terminal.

Prerequisites

• Gemini CLI installed (installation guide)
• A Toolcog account (sign up)

Configuration

Gemini CLI uses a JSON settings file for MCP servers.

Settings File Location

Edit ~/.gemini/settings.json:

{
  "mcpServers": {
    "toolcog": {
      "url": "https://mcp.toolcog.com"
    }
  }
}

Using Toolcog

Start Gemini CLI and ask:

gemini

Then in the session:

“@toolcog Find operations for creating Stripe invoices”

Or without the prefix:

“What HubSpot operations are available for contacts?”

Gemini will use Toolcog to discover operations, show interfaces, and help you execute them.

Authentication

When Gemini needs to access your Toolcog account:

1. Gemini displays an authorization link
2. Open the link in your browser
3. Sign in to Toolcog
4. Return to Gemini CLI

For downstream services (Stripe, HubSpot, etc.), the same pattern applies.

Catalogs

Connect to specific catalogs:

{
  "mcpServers": {
    "toolcog-internal": {
      "url": "https://mcp.toolcog.com/mycompany/internal-apis"
    }
  }
}

Google’s Managed MCP Servers

Google offers managed MCP servers for Google services (Maps, BigQuery, GCE, GKE). You can use these alongside Toolcog for comprehensive access to both Google and third-party APIs.

Verify It’s Working

In Gemini CLI, ask:

“What operations does Toolcog have for Zendesk?”

If you see a list of operations, Toolcog is connected.

Troubleshooting

Server not connecting

• Verify your settings.json is valid JSON
• Check the file is in ~/.gemini/settings.json
• Restart Gemini CLI after config changes

Tools not appearing

• Ensure Toolcog is listed in your settings.json
• Try using the @toolcog prefix explicitly

Authentication errors

• Click the authorization link to sign in to Toolcog
• Verify you’re signed in at toolcog.com

Next Steps

• Quick Start — Your first API operation
• API Meta-Tools — How discovery, learning, and execution work