Gemini

Use this guide when you want Gemini CLI or Gemini Code Assist agent mode to call FITsociety MCP tools.

Prerequisites

Before connecting, make sure:

your company has the mcp feature enabled
a Manager or Admin coach has created an MCP grant (OAuth consent or a static MCP API key) for the access you need

See Setup for Coaches for how to enable the feature and create a grant.

Server URL

https://mcp.fitsociety.io/mcp/v1

Gemini CLI configuration

Gemini CLI reads MCP servers from settings.json. User-level settings:

~/.gemini/settings.json

Project-level settings:

.gemini/settings.json

Add:

{
  "mcpServers": {
    "fitsociety": {
      "httpUrl": "https://mcp.fitsociety.io/mcp/v1"
    }
  }
}

Authentication

Gemini CLI supports remote MCP authentication for HTTP transports. Prefer OAuth when Gemini starts the FITsociety authorization flow. If you use a static company MCP API key, configure an authorization header:

{
  "mcpServers": {
    "fitsociety": {
      "httpUrl": "https://mcp.fitsociety.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer YOUR_FITSOCIETY_MCP_KEY"
      }
    }
  }
}

Keep static keys out of committed settings files. Use user-level settings or environment-specific secret management for real credentials.

Gemini Code Assist

For Gemini Code Assist agent mode, add the same MCP server configuration to the Gemini settings file used by your IDE integration.

Verify

Ask Gemini:

Use the FITsociety MCP server and list the available tools.

If no tools appear, verify the grant, bearer credential, MCP access, and owner coach role.

Get started

Connect your AI client

Concepts

Tools

Workflows

Reference & operations

Prerequisites

Server URL

Gemini CLI configuration

Authentication

Gemini Code Assist

Verify

​Prerequisites

​Server URL

​Gemini CLI configuration

​Authentication

​Gemini Code Assist

​Verify

Prerequisites

Server URL

Gemini CLI configuration

Authentication

Gemini Code Assist

Verify