Connect Unitag to Gemini
Gemini is two different situations, and it is worth being clear about which one you are in.
The Gemini app — gemini.google.com and the mobile apps — connects to other services through extensions that Google builds and ships. It does not yet take an arbitrary third-party connector with its own sign-in, so the Unitag connector cannot be added there. Gemini CLI can, and does it well.
Gemini CLI
Gemini CLI is Google's free terminal assistant. It supports the Model Context Protocol, which is what the Unitag connector speaks. Add it with one command:
gemini mcp add --transport http unitag https://mcp.unitag.io/mcp
The command does not take the client ID, so add it by hand before you sign in. Open Gemini CLI's settings file, find the unitag entry among its MCP servers, and add an oauth block to it:
"oauth": { "enabled": true, "clientId": "42deo5aspdubqjubemlal7iv54" }
Then start Gemini CLI and check the connection with the /mcp command, which lists the servers it knows about and whether each is signed in. If Unitag is listed but not authenticated, /mcp auth unitag opens the Unitag sign-in page in your browser.
From there it works like the others: ask a question in ordinary words, and approve any step that changes something in your account.
In the Gemini app
Without the connector, Gemini can still be made to answer Unitag questions accurately — from the documentation rather than from your account. Every page of this site has a plain-text twin written for exactly that.
Create a Gem, and in its instructions tell it to answer Unitag questions from the index at the address below, following the links it lists.
https://www.unitag.io/documentation/llms.txt
What this gives you is a reliable answer about the product. It cannot see your QR codes, your scan data or your campaigns, and it cannot change anything — for that you need the connector.
Gemini Enterprise and Vertex AI
If your organisation builds its own agents on Google's platform rather than using the consumer app, the Unitag connector is available there on the same terms as anywhere else: it is a standard MCP server with OAuth sign-in, and the address and client ID are the same.
If it does not work
The command is not recognised. Check your Gemini CLI is recent — MCP support and the
mcpsubcommand are not in the earliest releases.Unitag is listed but disconnected. Check that the
oauthblock with the client ID is in the settings file, then run the authentication command; the sign-in opens in your browser and the terminal picks it up when you are done.It says it cannot see something. The connector has your permissions. If the data is in a sub-organisation your account cannot reach, the assistant cannot reach it either.