Getting started

Two things to do, once: connect the Zywave MCP to your AI tool, then add the skills you want. About ten minutes, no developer.

Zywave supports the paid and enterprise versions of Claude, Microsoft Copilot, ChatGPT, and Google Gemini Enterprise. Free plans are not supported.

Add the Zywave MCP as a custom connector, then add skills per chat.

1. Connect the Zywave MCP to Claude

Do this once per person — or once per tenant, if your admin sets it up. Every skill in the catalog reuses the same connector.

Open connector settings In Claude, open Settings and find the connectors section, then choose to add a custom connector.
Paste the Zywave MCP server URL Use the server URL in the connection details above. Leave the transport at the default; the Zywave MCP speaks streamable HTTP and does not support the older SSE transport.
Sign in to Zywave and approve the scopes Claude hands you off to auth.zywave.com to complete the OAuth 2.1 + PKCE sign-in. Approve the scopes listed in the connection details above.

Menu labels move between Claude releases. If you cannot find the connector screen, search settings for "connector".

2. Add a skill

Repeat this whenever you want another skill. Every skill page has the same action.

Pick a skill from the Skills Library Filter by your role, or by what each skill needs from you. Browse the Skills Library →
Open its deploy guide for Claude Every skill page has a Claude link in its sidebar, which walks the same three steps for that specific skill.
Paste its example prompt Every entry ships one that works as written. Swap the names, states, and numbers for your own.

One-click install is not built. “Add a skill” means pasting instructions today — when the button exists, the prompts do not change.

Check that it worked

Paste this into a new Claude chat. You should get a tool list and five real accounts back.

Which Zywave tools can you use? Then show me my five most recently updated accounts.

Verification prompt quoted from the Zywave MCP Skills Library prototype’s setup page.

Zywave is in the Microsoft 365 Agent Store. Add the Zywave agent from there and it comes with the Zywave MCP already connected, with no server URL to paste.

1. Add the Zywave agent to Microsoft Copilot

Do this once per person. The agent brings the Zywave MCP connection with it, so there is nothing else to configure.

Open in the Microsoft 365 Agent Store

Open the Zywave agent in the Agent Store Use the Open in the Agent Store button above while signed in to your work account. To find it yourself instead, open Microsoft 365 Copilot, select Agents in the left pane, choose All agents, and search for Zywave.
Choose Add The Zywave agent then appears under Agents in the left pane of Microsoft 365 Copilot, and in Copilot inside Teams and Outlook.
Sign in to Zywave when asked The first time the agent needs Zywave data, it sends you to auth.zywave.com to sign in and approve access.

If the Zywave agent does not show up or Add is unavailable, your organization controls which store agents users can install. A Microsoft 365 admin can make it available in the Microsoft 365 admin center under Agents → All agents → Users, either for everyone or for specific groups.

2. Add a skill

Repeat this whenever you want another skill. Every skill page has the same action.

Pick a skill from the Skills Library Filter by your role, or by what each skill needs from you. Browse the Skills Library →
Open its deploy guide for Microsoft Copilot Every skill page has a Microsoft Copilot link in its sidebar, which walks the same three steps for that specific skill.
Paste its example prompt Every entry ships one that works as written. Swap the names, states, and numbers for your own.

One-click install is not built. “Add a skill” means pasting instructions today — when the button exists, the prompts do not change.

Check that it worked

Paste this into a new Microsoft Copilot chat. You should get a tool list and five real accounts back.

Which Zywave tools can you use? Then show me my five most recently updated accounts.

Verification prompt quoted from the Zywave MCP Skills Library prototype’s setup page.

Custom setup

Skip this if you added the Zywave agent above. It is for connecting the Zywave MCP server to Microsoft Copilot by hand — for example, to use it from an agent your organization builds itself.

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.

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.

A workspace admin approves the connector once, then it is available to workspace members.

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.

1. Connect the Zywave MCP to ChatGPT

Do this once per person — or once per tenant, if your admin sets it up. Every skill in the catalog reuses the same connector.

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.

2. Add a skill

Repeat this whenever you want another skill. Every skill page has the same action.

Pick a skill from the Skills Library Filter by your role, or by what each skill needs from you. Browse the Skills Library →
Open its deploy guide for ChatGPT Every skill page has a ChatGPT link in its sidebar, which walks the same three steps for that specific skill.
Paste its example prompt Every entry ships one that works as written. Swap the names, states, and numbers for your own.

One-click install is not built. “Add a skill” means pasting instructions today — when the button exists, the prompts do not change.

Check that it worked

Paste this into a new ChatGPT chat. You should get a tool list and five real accounts back.

Which Zywave tools can you use? Then show me my five most recently updated accounts.

Verification prompt quoted from the Zywave MCP Skills Library prototype’s setup page.

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.

1. Connect the Zywave MCP to Google Gemini Enterprise

Do this once per person — or once per tenant, if your admin sets it up. Every skill in the catalog reuses the same connector.

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.
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.
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).
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.
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.

2. Add a skill

Repeat this whenever you want another skill. Every skill page has the same action.

Pick a skill from the Skills Library Filter by your role, or by what each skill needs from you. Browse the Skills Library →
Open its deploy guide for Google Gemini Enterprise Every skill page has a Google Gemini Enterprise link in its sidebar, which walks the same three steps for that specific skill.
Paste its example prompt Every entry ships one that works as written. Swap the names, states, and numbers for your own.

One-click install is not built. “Add a skill” means pasting instructions today — when the button exists, the prompts do not change.

Check that it worked

Paste this into a new Google Gemini Enterprise chat. You should get a tool list and five real accounts back.

Which Zywave tools can you use? Then show me my five most recently updated accounts.

Verification prompt quoted from the Zywave MCP Skills Library prototype’s setup page.

Custom integrations talk to the MCP server directly — start from the MCP Apps reference instead.