An admin registers and approves the connector once for the tenant, then it is available to users.
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 Territory market map
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 Microsoft Copilot’s exact steps, or open territory-market-map’s skill folder directly.
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 territory (states, a city, or a radius) and the line of business
3. Paste the example prompt
In a new Microsoft Copilot chat, paste this. Swap the names, states, and numbers for your own.
Map the commercial market in Minnesota, who's out there, when they renew, who holds them, and where we already are.
Source: Written for this skill by the R&D AI Experience team.
Counts are facts; sample-derived figures are labeled estimates. A null broker field is shown as “no data,” never as unrepresented. Reduced-grid live run Sep 2026. DOT and OSHA counts mean “has a compliance record on file,” not violations; the CRM overlay currently runs client-side while a platform filter defect is open.
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.