Connect Gemini CLI

MCP Endpoint

URL

https://ai-mcp.insyncanalytics.com/mcp

Config File

Gemini CLI reads MCP server configuration from:

bash

~/.gemini/settings.json

Create the file if it does not exist.

Configuration Block

Gemini CLI reads MCP server configuration from:

json

{
  "mcpServers": {
    "insync-analytics": {
      "httpUrl": "https://ai-mcp.insyncanalytics.com/mcp",
      "timeout": 30000
    }
  }
}

Important: Gemini CLI uses "httpUrl" — not "url" as used by Claude Desktop and VS Code. Using the wrong key will result in the server not being recognized.

Setup Steps

Open or create ~/.gemini/settings.json`.
Add the configuration block above. If the file already has other content, merge the "mcpServers" section.
Save the file.
Start (or restart) Gemini CLI.
On first financial data query, a browser window will open for OAuth authentication.
Log in with your InSync Analytics credentials. The token is stored automatically.

Authentication Flow

Gemini CLI handles OAuth via the same redirect flow as other clients:

First request requiring financial data → browser opens.
Log in at the InSync authentication page.
Log in with your InSync Analytics credentials.
Browser redirects back → token stored in Gemini CLI's session.

Tokens refresh automatically on subsequent sessions.

Verification

After setup, run Gemini CLI and ask: "What financial data tools are available?"

The response should reference insync_assistant and list InSync's financial data capabilities.

Troubleshooting

See Troubleshooting → Gemini CLI section