Gemini - FITsociety Developer APIs

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

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, feature flag, and owner coach role.

​Server URL

​Gemini CLI configuration

​Authentication

​Gemini Code Assist

​Verify

Server URL

Gemini CLI configuration

Authentication

Gemini Code Assist

Verify