An admin registers and approves the connector once for the tenant, then it is available to users.
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.
Microsoft Copilot needs an admin. A Zywave administrator registers the client and your own Microsoft Copilot 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 Microsoft Copilot
- Ask your admin to register the client. The Zywave MCP does not support Dynamic Client Registration, so a Zywave administrator registers Copilot in the Zywave Admin tool and issues the client ID and redirect URI.
- Admin adds the connector for the tenant. Your Microsoft 365 admin adds the Zywave MCP server URL as an approved connector. Users cannot self-serve this step.
- Sign in to Zywave and approve the scopes. The first time you use it, Copilot sends you to auth.zywave.com to complete the OAuth 2.1 + PKCE sign-in for the scopes listed in the connection details above.
Tenant policy decides whether users can see the connector at all. If it is missing after your admin adds it, that is the place to look.
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 Renewal prep agent
This entry is catalog-only so far. Adding Renewal prep agent means giving your AI client the instructions in plain language:
Use the Zywave MCP for this task. Works a renewal list from end to end. Pulls the accounts renewing and assembles the notice packets.
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:
- The renewal window you care about
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 Microsoft Copilot chat, paste this. Swap the names, states, and numbers for your own.
Pull my benefits clients renewing in Q4 and assemble their annual notice packets.
Source: Placeholder prompt, composed from the notice-packet skill applied across a list. Not from the Prompt Library.
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.