Proxaradocs
Guides/Set up your AI

Proxara in Gemini

Connect through Gemini Enterprise. Authorize once in chat.

Updated August 2026

Proxara connects to Gemini Enterprise, including its Business edition. The everyday Gemini app, on a phone or at gemini.google.com, cannot add custom connectors, so it is not a path today.

Your Google admin connects Proxara once. You authorize it in the chat box, in about a minute, with the Microsoft work sign-in you already use. Nothing installs.

Gemini Enterprise
What is still missing for the 1120-S engagement?

Two documents are still open for [Organization_0599F9C6AF50]. The signed engagement letter is filed. [Person_0CE2473EA47B] was asked for the outstanding K-1 on Friday and has not replied.

Stand-ins in the answer; real names in the private view
The admin connects Proxara once in Connected apps; each person authorizes it in the chat box

Step 1. The admin connects Proxara

One form, for the whole firm: Manage team, then Connected apps, then Add MCP Server.

For the Google admin: what the form asks for

Google labels the feature a preview. MCP is the open standard AI tools use to reach outside systems, and the form only asks for what Proxara hands over at onboarding.

MCP info takes the firm's connector address, a web address ending in /mcp, plus a name and a one-line description.

Authentication settings takes the sign-in details Proxara provides with the address: an authorization address, a token address, a client ID, and a client secret. Claude and ChatGPT register themselves the first time they connect; Gemini asks for these up front instead.

Click Add and the connection appears on the Connected apps page, switched off. It stays invisible until the admin turns it on, and everything it can do arrives as an action that is also off. Nothing runs beyond the reviewed set the admin enables.

Gemini reaches the connector over the public internet. The address Proxara provisions is built for that, one HTTPS address, with the firm's client data staying inside the firm's environment behind it.

A firm on the standard edition does the same work in the Google Cloud console, where the connection is also attached to the team's Gemini app.

Access follows Microsoft Entra. Revoke a person there and their access ends in Gemini and in every other assistant at once.

Step 2. You authorize it in the chat box

Open the connectors icon, find Proxara, click Authorize. The sign-in is your Microsoft work account, not your Gemini one. The switch then stays on.

What comes back

Answers carry stand-ins in place of client names. Real names appear in the private view, under your own sign-in.

Gemini asks you to confirm anything that is not read-only, so a draft never becomes a send on its own.

You're connected

Ask where one of your engagements stands. A right answer that uses a stand-in for the client name means it is working.

If something doesn't work

  • Proxara not in the connectors list? It stays invisible until the admin switches it on.
  • An action you expected is missing? Every action starts off until an admin enables it.
  • Sign-in refused? It wants your Microsoft work account. A Gemini login on its own gets nothing.

Where to go next

To understandRead
What the model receives, and never receivesHow Proxara works
First requests that work on day oneWhat to ask for
The same setup in the other assistantsClaude, ChatGPT, Copilot