Before you connect

Sign in to Citera and open Settings → API & MCP → MCP. Select Connect another assistant. Choose your client, or Other client when it is not listed, and copy the server URL. API and MCP access are open to all Citera accounts.

Open Citera API & MCP settings

The current server URL is https://mcp.citeralabs.ai/mcp. Browser sign-in lets you select the brands your assistant may read without creating an API key. The connection is read-only; it does not grant content generation or publishing access.

Configure the remote HTTP server

Use Gemini CLI rather than assuming the Gemini chat website has the same configuration. Merge the following entry into the mcpServers object of your personal ~/.gemini/settings.json. Keep other servers and settings.

{
  "mcpServers": {
    "citera": {
      "httpUrl": "https://mcp.citeralabs.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "citera": {
      "httpUrl": "https://mcp.citeralabs.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "citera": {
      "httpUrl": "https://mcp.citeralabs.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "citera": {
      "httpUrl": "https://mcp.citeralabs.ai/mcp"
    }
  }
}

Sign in

Restart Gemini CLI or reload its MCP connections. Open /mcp to inspect Citera, then use /mcp auth citera when sign-in is required. Complete browser sign-in to Citera and select the brands it may read.

Verify the connection

Enable Citera in your client and send this first request. Inspect the Citera tool result: it should list only brands you authorized. A written answer without a Citera tool call does not verify a connection.

Use the Citera MCP tools to list the brands I authorized. Show their names and IDs. Then ask which brand I want to review. Do not change, generate or publish anything.

Permissions, limits and troubleshooting

OAuth needs a browser and a reachable local callback on the machine running Gemini CLI. A headless container or remote shell may not support that flow. If it cannot complete sign-in, use the manual-key instructions in the shared client setup guide with a client configuration that supports Authorization headers. Do not enable trust merely to suppress connection errors.

A brand with no completed scans may have little visibility data to report. If a brand is missing, check the account used for sign-in and the brands selected during consent. Reconnect when needed. You can revoke the connection under AI assistants in Citera’s MCP settings. API and MCP share the account’s applicable usage allowance.

Client menus, plan requirements and connection capabilities can evolve. These instructions describe configuration and a verification step; they do not guarantee that every client version or workspace policy allows the connection.

Try a complete workflow

Weekly AI visibility brief

White label client report

Find pages losing visibility

Client reference

Official Gemini CLI documentation