A workspace admin approves the connector once, then it is available to workspace members.
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.
ChatGPT needs an admin. A Zywave administrator registers the client and your own ChatGPT 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 ChatGPT
- Ask your admin to register the client. A Zywave administrator registers ChatGPT in the Zywave Admin tool and issues the client ID and redirect URI. There is no Dynamic Client Registration.
- Admin adds the connector to the workspace. Your ChatGPT workspace admin adds the Zywave MCP server URL as a connector so members can enable it.
- Sign in to Zywave and approve the scopes. Enable the connector in a chat and complete the OAuth 2.1 + PKCE sign-in at auth.zywave.com for the scopes listed in the connection details above.
Available on ChatGPT plans that support workspace connectors. Confirm with your admin before you plan a rollout.
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 Prospecting campaign agent
This entry is catalog-only so far. Adding Prospecting campaign agent means giving your AI client the instructions in plain language:
Use the Zywave MCP for this task. Runs a prospecting campaign end to end. Finds the segment, drafts the touches, and stops for your review before anything sends.
What it needs from you: A few details from you. You supply the specifics in the prompt, company, state, size, dates.
Details to fill in when you run it:
- The segment to campaign to, and the send window you want
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 ChatGPT chat, paste this. Swap the names, states, and numbers for your own.
Build a 3-touch email campaign to the self-funded prospects we just found.
Source: Verbatim from the Prompt Library (Employee Benefits · Launch a prospecting campaign). The agent around it is placeholder.
Sending is a write action. Nothing should leave your agency without an explicit approval step.
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
← Pick a different client · Back to Prospecting campaign agent