> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fitsociety.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Gemini

> Use Gemini CLI or Gemini Code Assist with FITsociety MCP.

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](/mcp/setup-for-coaches) for how to enable the feature
and create a grant.

## Server URL

```text theme={null}
https://mcp.fitsociety.io/mcp/v1
```

## Gemini CLI configuration

Gemini CLI reads MCP servers from `settings.json`.

User-level settings:

```text theme={null}
~/.gemini/settings.json
```

Project-level settings:

```text theme={null}
.gemini/settings.json
```

Add:

```json theme={null}
{
  "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:

```json theme={null}
{
  "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:

```text theme={null}
Use the FITsociety MCP server and list the available tools.
```

If no tools appear, verify the grant, bearer credential, feature flag, and owner
coach role.