A Google Cloud admin allows custom MCP connectors for the organization and adds the Zywave MCP as a data store, then users sign in.

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

FieldValue
Server URLhttps://ai.zywave.com/mcp/v1
TransportStreamable HTTP (Server-sent events (SSE) is not supported.)
Protocol version2025-03-26
AuthenticationOAuth 2.1 with PKCE (S256 challenge method)
Authorization endpointhttps://auth.zywave.com/connect/authorize
Token endpointhttps://auth.zywave.com/connect/token
Revocation endpointhttps://auth.zywave.com/connect/revocation
Scopesmcp, api.accounts, api.content, api.companies, offline_access (optional)
Client registrationManual. 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

  1. 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.
  2. 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.
  3. 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).
  4. 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.
  5. 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 Contact enrichment refresh

Published in the public Zywave/skills marketplace. From a terminal: gh skill install Zywave/skills --all installs every skill there, this one included, into 49+ AI clients. In Claude Desktop or Code, add the marketplace once (/plugin marketplace add Zywave/skills) and install the zywave-skills plugin. See the full install guide for Google Gemini Enterprise’s exact steps, or open contact-enrichment-refresh’s skill folder directly.

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:

  • A segment, a list of accounts, or nothing for the whole book

3. Paste the example prompt

In a new Google Gemini Enterprise chat, paste this. Swap the names, states, and numbers for your own.

Refresh the decision-maker contacts on our Minnesota commercial accounts that have no email on file. Show me the cost first.

Source: Written for this skill by the R&D AI Experience team.

Preview is free, enrichment is metered, and the producer approves the exact scope between the two. Writes to the CRM and has not yet been live-evaluated; validate in the sandbox tenant before using on production data.

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.

Next

It worked. What now? →

← Pick a different client · Back to Contact enrichment refresh