An MCP app is any AI client you have connected to the Zywave MCP Server: Claude, Microsoft Copilot, ChatGPT, or something you built yourself. Connect it once and every skill in the catalog works in it.
If you are setting up a documented client, you want the deploy flow, which walks these same values in order. This page is the flat reference: the fields an admin or an integration developer asks for.
Connection reference
| 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. |
Scopes
| Scope | Required | Purpose |
|---|---|---|
mcp | Yes | Access the MCP server itself. Every client needs this. |
api.accounts | Yes | Accounts and contacts, the book-of-business tools. |
api.content | Yes | The Zywave content library, resource and grounded-answer tools. |
api.companies | Yes | Company and market data, prospecting and research-brief tools. |
offline_access | Optional | Issues a refresh token so the client does not re-prompt every session. |
Scope names are from the Zywave MCP documentation. The purposes are our reading of which tool area each one serves, not documented wording.
Tools
22 tools, across four functional areas:
- Book of business
- Prospecting
- Content library
- Research briefs
Plus a session-identity utility. Read tools carry readOnlyHint; write tools carry destructiveHint and expect an explicit confirmation before they run.
Source: Zywave MCP Server documentation.
Registering a client
There is no Dynamic Client Registration. A Zywave administrator registers each client in the Zywave Admin tool and issues the client ID and redirect URI, so adding a new MCP app is an administrative step, not a self-service one. For Microsoft Copilot and ChatGPT you also need an admin on that side to approve the connector for your tenant or workspace.
Safety model
Tool annotations do the work here, and they matter for how you write skills:
- Read tools carry
readOnlyHint. They can be called freely: the Book of business audit skill makes no writes to Zywave at all, by design. - Write tools carry
destructiveHintand expect an explicit confirmation before they run. A well-behaved client asks you first. Do not design a skill that assumes writes happen silently, and do not assume bulk writes work: the confirmation is per call.
Custom integrations
Anything that speaks MCP over streamable HTTP and can complete an OAuth 2.1 + PKCE (S256) authorization code flow can connect. Two things catch people out:
- The older SSE transport is not supported. If your client library defaults to server-sent events, switch it to streamable HTTP.
- Pin the protocol version. The server speaks
2025-03-26. A client that negotiates a different version may not connect.
Ask for offline_access alongside the other scopes if your integration runs
unattended and cannot re-prompt a human for consent.
What this page does not cover
For the requirements doc:
- Whether an MCP app is configured per user or per tenant, and what an agency admin actually sees and sets in the Zywave Admin tool.
- The individual tool names, arguments, and rate limits. Only the four functional areas and the tool count are public in the source we have.
- How a Zywave-hosted agent would authenticate, given that today’s model assumes a human completing an interactive consent flow.
- The tool-count discrepancy: the Zywave MCP documentation says 22 tools; the Skills Library prototype’s stat callout says 28. This page follows the API documentation.