Gemini (CLI)

Add Trunk’s MCP Server to Gemini

CLI setup

Run the following command to add the MCP server configuration. If you want to only enable it for yourself, use --scope user instead.

gemini mcp add --transport http trunk https://mcp.trunk.io/mcp --scope project

Once completed, reopen Gemini.

Alternative: Update MCP configuration

Add the following configuration to your project’s .gemini/settings.json file.

{
  "mcpServers": {
    "trunk": {
      "httpUrl": "https://mcp.trunk.io/mcp"
    }
  }
}

Authentication with OAuth (default)

After the MCP server was added to Gemini, users need to authorize to communicate with the server. Follow these steps to complete auth.

Step 1: Start Gemini CLI

In your terminal, run gemini .

Step 2: Run the mcp auth command

Run /mcp auth trunk to initiate the authentication and authorization flow.

Step 3: Login & authorize

A new webpage will be opened. Log in with your Trunk account and follow the instructions to authorize Gemini to communicate with the MCP server.

Step 4: Confirm

Follow instructions to get back to Gemini. A confirmation should be shown:

ℹ✅ Successfully authenticated with MCP server 'trunk'!

ℹRe-discovering tools from 'trunk'...

ℹSuccessfully authenticated and refreshed tools for 'trunk'.

With auth completed, Gemini will be able to fetch the tools exposed by Trunk’s MCP server.

Alternative: Authentication with API token

If you prefer not to use the OAuth flow, you can authenticate with your Trunk organization API token. Find your token under Settings > API in the Trunk dashboard.

Add the token to your .gemini/settings.json:

{
  "mcpServers": {
    "trunk": {
      "httpUrl": "https://mcp.trunk.io/mcp",
      "headers": {
        "Authorization": "Bearer ${TRUNK_API_TOKEN}"
      }
    }
  }
}

Set TRUNK_API_TOKEN as an environment variable. Gemini CLI interpolates environment variables in MCP configuration files automatically.