Connect / Gemini

Connect Gemini to Telara

Gemini Enterprise reaches Telara through the Google Cloud Marketplace AI-agent route. Each employee completes Telara OAuth once; no API key, MCP configuration, or tenant-specific endpoint is required.

client_type: gemini

The endpoint

Streamable HTTPhttps://api.telara.dev/v1/mcp

AuthOAuth 2.1 + PKCE with dynamic client registration

Connect it yourself

After the Google Cloud Marketplace listing is available to your organization, employees add Telara from Gemini Enterprise and sign in to Telara once.

Select Telara from your organization’s approved Gemini Enterprise agents or Marketplace catalog.

Choose Connect and complete the Telara OAuth authorization page with your work identity.

Return to Gemini and use Telara on information or work you are individually authorized to access.

Rolling it out centrally

Google Cloud Marketplace vendor onboarding and an AI-agent listing are the official distribution path. Google controls the vendor, pricing, technical-integration, and listing reviews.

A Google Partner Admin completes the Cloud Marketplace vendor agreement and receives Producer Portal access.

Telara submits its A2A Agent Card, product details, pricing, and technical-integration reviews in Producer Portal.

After Google approves the listing, a customer administrator makes Telara available in Gemini Enterprise; each employee still authorizes their own Telara access.

Before you commit to this

Marketplace approval is not an MCP setting

Google’s public AI-agent route requires Marketplace vendor onboarding and Producer Portal review. A hand-authored CLI configuration is not the employee one-click deployment path.

Agentspace traffic classifies as gemini

Both the CLI and Agentspace write audit rows classified as gemini or agentspace, so attribution holds across the two paths and a pilot’s evidence stays valid after the managed rollout.

Confirm it actually worked

The client's “connected” badge reports a successful handshake, not a tool call. Ask Gemini something answerable only from your indexed Telara data, then read GET /v1/mcp/audit/log and look for a row with client_type=gemini.

An answer with no matching audit row means the assistant replied from its own knowledge and never called Telara — a routing problem in the tool descriptions, not a broken connection. Every transport check will still look green.

Support, privacy, and reviewer testing

The complete OAuth and platform-review guide defines the governed 21-tool contract, the reviewer test flow, and the safe test action for platforms that permit writes.

For setup or reviewer access, contact support@telara.dev. For privacy requests, contact privacy@telara.dev. Telara's Privacy Policy and Terms of Service apply to every connection.

Comparing platforms? See connection paths for what each one needs. Looking instead to let Telara readthis platform's usage and spend? That is the opposite direction — see the connector catalog.