Connect Gemini to digna¶

This guide connects Google's Gemini tools to the digna MCP Server. You need the MCP endpoint of your digna installation and an API key, as described in the AI Agents Overview.

The examples use https://digna.example.com/mcp as the endpoint. Replace it with yours.

Choose Your Tool¶

All of these tools connect from the machine they run on, so they work with digna inside your company network as long as that machine can reach the endpoint.

Antigravity¶

Antigravity reads its MCP servers from mcp_config.json, shared by the CLI, the IDE and the app.

1. Open mcp_config.json¶

To open the file in use:

• CLI: type /mcp and press Enter to open the MCP manager.
• IDE: in the agent side panel, open the … menu, select MCP Servers, then Manage MCP Servers, then View raw config.
• App: go to Customizations > Installed > MCP Servers and use Copy Config File Path.

2. Add the digna Server¶

Add the digna entry. If the file already has an mcpServers section, add it there:

{
  "mcpServers": {
    "digna": {
      "serverUrl": "https://digna.example.com/mcp",
      "headers": {
        "Authorization": "Bearer <api key>"
      }
    }
  }
}

Antigravity reaches remote servers only over streamable HTTP, which the digna MCP Server uses. Write the endpoint as serverUrl; the httpUrl key of Gemini CLI is not supported.

3. Verify the Connection¶

In the CLI, type /mcp: the MCP manager shows the digna server with its status and tools, and can reload the configuration and show connection logs. In the IDE, the server appears under Manage MCP Servers.

Gemini CLI¶

1. Add the Server¶

Put the API key in an environment variable, then add the server:

export DIGNA_API_KEY='<api key>'
gemini mcp add --transport http --scope user --header "Authorization: Bearer $DIGNA_API_KEY" digna https://digna.example.com/mcp

Your shell fills in $DIGNA_API_KEY when you run the command, so Gemini CLI stores the key in its settings. Without --scope user, the server is added to the current project only.

2. Or Edit settings.json¶

The command above writes to settings.json. To edit the file yourself:

{
  "mcpServers": {
    "digna": {
      "httpUrl": "https://digna.example.com/mcp",
      "headers": {
        "Authorization": "Bearer <api key>"
      }
    }
  }
}

Use httpUrl, the key for streamable HTTP. The similar url key selects the older SSE transport, which the digna MCP Server does not offer. Don't use underscores in the server name.

3. Verify the Connection¶

From your shell:

gemini mcp list

The digna server must show as connected. Inside a Gemini CLI session, run /mcp to see the server and its tools.

Troubleshooting Gemini¶

The server shows as disconnected¶

• Check that the endpoint ends in /mcp and is reachable from your machine.
• Check the key name: serverUrl in Antigravity, httpUrl in Gemini CLI.
• A 401 means the key was rejected; see 401 Unauthorized.

Gemini CLI no longer starts for my account¶

Since June 2026, individual Google accounts use Antigravity CLI instead of Gemini CLI. Move the digna entry to mcp_config.json as described under Antigravity, and rename httpUrl to serverUrl.

See Also¶

• AI Agents Overview: endpoint, API key, security and general troubleshooting
• Claude: connect Claude Code, Claude Desktop or a custom connector
• digna Agentic: what AI agents can do with digna