Skip to main content
Gemini Enterprise connects to CodeQR as a custom MCP server. It differs from the clients in the introduction in one way that changes the setup: it asks for a client ID up front instead of registering itself, so you create one first with a single command.
Gemini Enterprise supports Streamable HTTP only — the transport CodeQR speaks. The legacy SSE transport is not supported by either side.

​
Step 1 — Create a client ID

Gemini Enterprise sends users back to a fixed callback URL after they sign in. Register that URL with CodeQR to get a client ID:
You get back a client_id starting with codeqr_. Keep it — you will paste it in step 2.
Register the callback URL exactly as Gemini Enterprise shows it in its setup screen. CodeQR checks the redirect URI against what you registered before it echoes anything back, so a mismatch fails the sign-in with redirect_uri does not match any URI registered for this client. If your tenant shows a different callback, register that one instead.

​
Step 2 — Add the MCP server

In Gemini Enterprise, go to Data stores → Create data store, choose Custom MCP Server, and fill in:
PKCE is mandatory. CodeQR treats every MCP client as public and relies on PKCE instead of a secret, so an authorization request without code_challenge_method=S256 is rejected before the user ever sees a login screen. If sign-in fails immediately with PKCE with S256 code_challenge_method is required, PKCE is off.

​
About the client secret

CodeQR does not issue one. The registration response says so — "token_endpoint_auth_method": "none" — and the token endpoint ignores the field entirely; it authenticates the exchange with PKCE and the registered redirect URI. Gemini Enterprise marks the field as required, so put any placeholder in it. It is neither sent anywhere meaningful nor checked.

​
Step 3 — Enable the actions

Once the data store reaches Active, open it and choose Actions → Reload custom actions. Sign in to CodeQR and pick the project to grant access to. The fourteen CodeQR tools appear in the list. Select the ones your team should have and click Enable actions.
Start with the read-only tools — list_links, list_qrcodes, get_analytics, get_workspace — if you want the team exploring before anyone can change a live destination. You can enable the rest later without redoing the connection.

​
What your team gets

Approving the connection grants CodeQR access scoped to the single project chosen at sign-in: read and write on links, QR codes and tags, plus read on analytics and domains. Conversion tracking is not included — see the note on scopes. Gemini Enterprise caps a data store at 100 enabled actions; CodeQR uses fourteen, so there is room alongside other servers.

​
Troubleshooting

PKCE is off. Turn on Enable PKCE Support in the connection’s authentication settings. CodeQR rejects the authorization request outright without it.
The callback URL Gemini Enterprise uses is not one you registered in step 1. Copy the exact URL from its setup screen and re-run the registration command with it — you get a new client_id, which replaces the one in the connection.
Confirm the server is reachable from outside your network:
It should answer {"status":"ok","service":"codeqr-mcp-remote", ...}. Note that Private Service Connect and VPC Service Controls are not supported by this connector.
The action list is populated by Reload custom actions, not by the connection itself. Run it from the data store once it shows Active.