A Google Cloud admin allows custom MCP connectors for the organization and adds the Zywave MCP as a data store, then users sign in.
Caveat. This agent is placeholder content, so there is nothing published to add in step 2 yet. Step 1 below is real and worth doing anyway: the connector is shared by every entry in the catalog.
Google Gemini Enterprise needs an admin. A Zywave administrator registers the client and your own Google Gemini Enterprise admin approves the connector. Neither step is self-service, so start that conversation before you plan a rollout.
Connection details
| Field | Value |
|---|---|
| Server URL | https://ai.zywave.com/mcp/v1 |
| Transport | Streamable HTTP (Server-sent events (SSE) is not supported.) |
| Protocol version | 2025-03-26 |
| Authentication | OAuth 2.1 with PKCE (S256 challenge method) |
| Authorization endpoint | https://auth.zywave.com/connect/authorize |
| Token endpoint | https://auth.zywave.com/connect/token |
| Revocation endpoint | https://auth.zywave.com/connect/revocation |
| Scopes | mcp, api.accounts, api.content, api.companies, offline_access (optional) |
| Client registration | Manual. The server does not support Dynamic Client Registration, so a Zywave administrator registers each client in the Zywave Admin tool and issues the client ID and redirect URI. |
Full reference, including what each scope covers and what the 22 tools do: MCP Apps.
1. Connect the Zywave MCP to Google Gemini Enterprise
- Ask your admin to register the client. A Zywave administrator registers Gemini Enterprise in the Zywave Admin tool and issues the client ID and redirect URI. There is no Dynamic Client Registration.
- Admin allows custom MCP connectors. In the Google Cloud console, open IAM & Admin → Organization Policies (console.cloud.google.com/iam-admin/orgpolicies). Turn off the “Disable custom MCP server connector for Gemini Enterprise” policy, then edit “Restrict egress domains for data connectors” to allow ai.zywave.com and auth.zywave.com.
- Admin adds the Zywave MCP as a data store. Open Gemini Enterprise (console.cloud.google.com/gemini-enterprise), go to Connected data stores, choose New data store, and pick Custom MCP Server. Enter the server URL from the connection details above, the client ID from step 1, and the Zywave authorization and token endpoints (https://auth.zywave.com/connect/authorize and https://auth.zywave.com/connect/token).
- Admin enables the Zywave tools. Back in Connected data stores, open the Zywave data store and enable its tools under Actions. Until they are enabled, Gemini sees the connector but cannot call anything.
- Sign in to Zywave and approve the scopes. The first time you use it, Gemini sends you to auth.zywave.com to complete the OAuth 2.1 + PKCE sign-in for the scopes listed in the connection details above.
Both organization policies are required. If the data store will not save or cannot reach the server, check that the MCP connector policy is off and that both Zywave domains are on the egress allow list.
Do this once per person, or once per tenant if your admin sets it up. Every other skill in the catalog reuses the same connector.
2. Add Book hygiene agent
This entry is catalog-only so far. Adding Book hygiene agent means giving your AI client the instructions in plain language:
Use the Zywave MCP for this task. Walks your book looking for stale or missing data and proposes the fixes for you to approve.
What it needs from you: Nothing from your client. Everything it needs is already in Zywave. Run it and review the output.
Details to fill in when you run it:
- Nothing. It reads your book and proposes changes.
One-click install is not built. When it exists, this step becomes a button; the prompt below does not change.
3. Paste the example prompt
In a new Google Gemini Enterprise chat, paste this. Swap the names, states, and numbers for your own.
Find accounts in my book where the employee count looks out of date and show me what you would change.
Source: Placeholder prompt, in the shape of the Prompt Library’s “Update the employee count on [client]” prompt.
Bulk writes are the open question here. The MCP’s write tools confirm one call at a time.
Check that it worked
If nothing comes back, or the client says it has no tools, paste this instead. You should get a tool list and five real accounts.
Which Zywave tools can you use? Then show me my five most recently updated accounts.
Source: verbatim from the Zywave MCP Skills Library prototype’s setup page.