Kiteworks Agent Marketplace
Quel assistant IA utilisez-vous ?

Connecter Kiteworks à Gemini Enterprise

Configurez le connecteur Kiteworks MCP dans Gemini Enterprise : qui fait quoi, les étapes pour chaque rôle et comment vérifier que tout fonctionne.

Connect Kiteworks to your Gemini Enterprise app in Google Cloud. Your administrator creates the connection once; each user signs in with their own Kiteworks account.

Avant de commencer

Qui s’en charge : MCP server administrator

  • MCP server administrator The remote Kiteworks MCP server is deployed by the customer (not hosted per tenant); find or deploy it and note its host.
  • A Gemini Enterprise app in Google Cloud and permission to create data stores (roles/discoveryengine.editor).
  • Your organization's Kiteworks MCP server URL, using Streamable HTTP: https://<your-mcp-server-host>/mcp.
  • A pre-registered OAuth client for that MCP server, supplied by its owner.

For a public endpoint, use a publicly trusted TLS certificate. For a private endpoint or fixed outbound IP addresses, configure Agent Gateway and VPC connectivity first; custom trust anchors are supported on that route.

Need a server? Follow the Kiteworks remote deployment guide.

Admin Kiteworks

Qui s’en charge : Kiteworks admin, MCP server administrator

Enable Kiteworks MCP

  1. In the Kiteworks Admin Portal, open Application Setup > Apps and Plugins > Kiteworks MCP.
  2. Enable MCP and save.
  3. Register your remote MCP server's callback: https://<your-mcp-server-host>/oauth/callback (include its port when required).
  4. Allow the API scopes needed by your users.

These settings connect the MCP server to Kiteworks. The separate Gemini OAuth client is configured in the next step. User permissions still apply.

Kiteworks admin setup

Prepare the Gemini OAuth client

Ask the MCP server owner to provide an OAuth client registered for Gemini Enterprise at the MCP server's authorization server, with this callback:

Obtain the authorization URL, token URL, client ID, client secret, scopes and supported token authentication method. Request refresh-token access using the provider's supported scopes or parameters.

These must be credentials for the MCP connection. Keep the separate credentials used by the MCP server to connect to Kiteworks on that server.

Google OAuth configuration

Admin Gemini Enterprise

Qui s’en charge : Google Cloud admin Qui approuve : Google Cloud admin

Allow custom MCP data stores

If your project blocks custom MCP data stores, an administrator with roles/orgpolicy.policyAdmin must update the project policy:

  1. Open Organization Policies and select the project's scope.
  2. Open Disable custom MCP server connector for Gemini Enterprise.
  3. Select Manage Policy > Override parent's policy.
  4. Add a rule with enforcement OFF, then select Set Policy.

For projects with enforced connector policies or VPC Service Controls, allow custom_mcp and the domain names of the MCP, authorization and token endpoints. When using Agent Gateway, also allow the app to bind to that gateway.

Google organization policy requirements

Add the Kiteworks data store

  1. Open Gemini Enterprise > Apps > your app > Connected Data Stores > New data store.
  2. Find Custom MCP Server and select Add MCP server.
  3. For a private endpoint or fixed-IP egress, select Route egress through Agent Gateway and supply your app's engine resource name.
  4. Choose OAuth 2.0 and enter:
FieldValue
MCP Server URLYour remote MCP URL ending in /mcp
Authorization URLMCP authorization endpoint, without query parameters
Token URLMCP token endpoint
Client ID / Client SecretGemini client credentials from the MCP server owner
ScopesSpace-separated scopes supplied by that owner
  1. Enable PKCE Support for the Kiteworks OAuth flow. Set Use HTTP Basic Authentication to match the token endpoint: selected for client_secret_basic, cleared for client_secret_post. Put additional provider parameters in Authorization URL Parameters.
  2. Select Verify Auth, sign in and continue.
  3. Select the multi-region and connector name, then Create. Wait for Active before enabling actions.

Google data store setup

Enable Kiteworks actions

  1. Open the data store's Actions page.
  2. Select Reload custom actions and authenticate.
  3. Select the tools your users need, then Enable actions.

Actions start disabled. Enable up to 100 and reload the list after server tool changes.

Google action settings

Utilisateur final

Qui s’en charge : End user

Connect your account and start

  1. Open the Gemini Enterprise app your administrator shared.
  2. Ask: "Use Kiteworks to list the folders I can access."
  3. When prompted, sign in to Kiteworks and allow access.

The connector uses your Kiteworks permissions. Review requested changes before confirming them. Actions marked read-only can run without confirmation.

Using Gemini Enterprise agents

Vérifier que ça fonctionne

Qui s’en charge : End user

Open a new chat in the assistant and ask these two questions. Both only read.

The first answer names your Kiteworks account. The second lists the folders you can open. If either fails, go to Troubleshooting.

Ce que vous pouvez faire

Qui s’en charge : End user

Copiez un prompt et collez-le dans Gemini Enterprise.

Sécurité et circulation des données

  • With a connection using end-user credentials, Kiteworks applies that user's permissions. Shared credentials use the shared account instead.
  • Select only the tools the task needs. Some require a Kiteworks administrator; some additional tools depend on the server's destructive-tools setting.
  • Content retrieved into a conversation is processed by the AI provider under your organization's agreement. Review the provider's data-handling documentation below.
  • Remove the connection and revoke its authorization when access is no longer required.

Documentation du fournisseur

Dépannage

ProblemFix
Cannot create the data storeCheck roles/discoveryengine.editor and the project's custom MCP policy.
Verify Auth failsAsk the MCP server owner to check the Gemini client, callback, endpoints, scopes, PKCE and token authentication method.
Connection fails or stays inactiveCheck Streamable HTTP, TLS and endpoint reachability; for private servers, check Agent Gateway routing and trust anchors.
No tools are availableOpen Actions, reload the list and enable the required actions.
Repeated sign-in promptsCheck refresh-token access and session policy with the MCP server owner.
Permission denied in KiteworksCheck the signed-in user's permissions and the tenant's allowed MCP scopes.

Google setup and connection requirements

Questions fréquentes

Is this the Gemini consumer app?

This guide is for Gemini Enterprise in Google Cloud. Gemini Apps, Workspace and Gemini CLI have different setup paths.

Can it upload or download files on my computer?

The remote Kiteworks MCP server has no access to your computer's filesystem. Use its text-reading tools or download links; local transfers require a local Kiteworks connector.

Kiteworks deployment modes

Does it install the marketplace's Claude add-ons?

No. This connection exposes Kiteworks MCP tools. Claude add-ons remain a separate installation in Claude.