Connect Whop to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Whop, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Whop + Microsoft Copilot

Let your AI work with your Whop business: products and plans, memberships and license keys, members, payments, promo codes, experiences, forum posts and webhooks, with cancellations and refunds kept switched off until you enable them.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

WHOP_API_KEY, WHOP_ACCOUNT_ID

Step 1 — Get credentials

1. Open https://whop.com/dashboard, pick your business in the business switcher, then go to Developer → Account API Keys → Create.
2. Choose the permissions. The Admin role covers everything. For a narrower set, grant the read permissions of the tools you use: member:basic:read (memberships, members, license keys), access_pass:basic:read (products), plan:basic:read (plans), payment:basic:read (payments), promo_code:basic:read (promo codes), forum:read (forum posts), developer:manage_webhook (webhooks), company:balance:read (whop_get_account) and member:email:read to see member emails. Cancelling needs membership:cancel or member:manage, refunding needs payment:manage.
3. Copy the key into WHOP_API_KEY. Whop shows it only once.
4. Put your business id into WHOP_ACCOUNT_ID. It starts with biz_ and is in the dashboard URL (whop.com/dashboard/biz_.../); whop_get_account also returns it.

Key types: the connector expects an Account API key, which acts as your own business. An App API key also works; then WHOP_ACCOUNT_ID decides which business the account-level tools read. OAuth tokens and iframe user tokens are not supported.

What it reads: products and plans with prices, billing periods and trials (Whop now calls plans variants; their ids still start with plan_), memberships, members and public user profiles, whether a user has access to a product, an experience or the business, payments with line items and refunds, promo codes, experiences, forum posts and webhook endpoints (without their signing secrets). whop_validate_license_key checks a software license key sold through Whop and answers whether it is valid; it does not bind or reset the key.

Switched off at install: whop_cancel_membership and whop_refund_payment. Enable them in the connector settings only if the AI should cancel or refund. Even then, the AI confirms the exact membership or payment, the buyer, the amount and the timing with you first: a refund emails the buyer, claws back the affiliate commission and cannot be undone.

Personal data: memberships, members and payments include names, emails (with member:email:read) and phone numbers. The AI uses them only for your request.

Long lists: list tools return results page by page, and the AI asks for the next page while there are more.

Common errors: 401 means the key is wrong, deleted or incomplete. 403: the key lacks the permission named in the message, so add it under Developer → Account API Keys. 404: an unknown id or license key, or an object of another business. 400: an invalid parameter, for example an id with the wrong prefix; the message names it. 429: a rate limit; wait and retry once.

The connector does not create or edit products, plans and promo codes, and does not cover checkout links, payouts, chat and DM messages, apps, ads or financial reports.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Whop tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "How many active memberships do we have on our Pro plan on Whop, and how many are set to cancel at the end of the period?"
• "Show me last week's Whop payments, with refunds and failed charges listed separately."
• "Is this license key valid, and which product and plan does it belong to?"
• "Which Whop promo codes are active right now, and how many uses does each one have left?"

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse