How to Connect Payhip to Microsoft Copilot via MCP

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

Payhip + Microsoft Copilot

Manage your Payhip store's coupon codes and check software license keys from an AI agent: list and read coupons, create new ones with your approval, verify a buyer's license key and, when you allow it, disable, re-enable or count its activations.

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:

PAYHIP_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Payhip store and its API key. For license keys you also need a product with license keys switched on.

1. In Payhip open Settings → Developer and copy the API key.
2. Paste it alone into PAYHIP_API_KEY. The coupon tools use it.
3. Optional, for license keys: open the product in Payhip, tick Generate unique license keys if it is not on yet, and copy the product secret key shown below that checkbox into PAYHIP_PRODUCT_SECRET_KEY.
4. Install the connector and run payhip_list_coupons: it lists your coupon codes and confirms that the API key works. If you set a product secret key, run payhip_verify_license with a key one of your buyers received to check the license side too.

One licensed product per install: a product secret key belongs to one product. To check the keys of several products, install the connector once per product and give each install the product's name. Coupons work on every install, because they use the store's API key.

What it reads: your store's coupon codes with code, type (one product, all products or one collection), percent or amount off, start and end dates, minimum purchase, usage limit and notes; and, for the configured product, the state of a license key: whether it is enabled, the buyer's email, product and variant, how often it has been used and when it was issued.

Only coupons and license keys: Payhip's API covers just these two areas today. Products, sales, customers and payouts are not available through it.

Reading the data: amounts (amount off, minimum purchase) are in cents, and percent off is a percentage. An empty answer from payhip_verify_license means the key does not exist for this product. Payhip disables a key automatically when its purchase is refunded. A key's uses are a counter your software raises and lowers; Payhip does not enforce a limit, your software does.

Switched off at install: payhip_create_coupon, payhip_disable_license, payhip_enable_license, payhip_increase_license_usage and payhip_decrease_license_usage. A new coupon works at checkout as soon as it exists, and a disabled key locks the buyer out of your software until it is enabled again. Subscription products cannot get coupons through the API. An administrator turns on the ones you need.

Asks before every change: with a write tool switched on, the AI shows you the code, the discount and what it applies to, or the license key and what will happen to it, and waits for your yes.

Limits: coupon lists come in pages of up to 100, so for a large store the AI pages through them instead of asking for everything at once.

Common errors: 401 authentication_fail means the API key or the product secret key is wrong or missing: copy PAYHIP_API_KEY again from Settings → Developer, and for license tools check PAYHIP_PRODUCT_SECRET_KEY on the product page. Payhip's firewall challenges coupon calls from datacenter addresses, so coupon calls go out through AnythingMCP's outbound proxy where one is configured (as on AnythingMCP Cloud). On a self-hosted server without CONNECTOR_PROXY_URL, coupon calls may answer 403 with an HTML page.

The connector does not read products, sales, customers or payouts, and it does not issue refunds or new license keys.

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 Payhip 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

• "Is the license key 7XK2-9QPL-44MZ-H1TR valid? Who bought it, and how many times has it been used?"
• "List our coupon codes with the discount each one gives, and tell me which ones expire this month."
• "What are the conditions of the SUMMER25 coupon: minimum purchase, usage limit and which product it applies to?"
• "A buyer says their key stopped working after a refund. Check whether it is still enabled and which email it belongs to."
• "Which of our coupons apply to all products, and which only to one product or a collection?"

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