How to Connect Tabby to Microsoft Copilot via MCP

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

Tabby + Microsoft Copilot

Tabby buy now, pay later (UAE, Saudi Arabia, Kuwait): look up payments with their captures and refunds, checkout sessions, customer disputes and webhooks. Capture, refund and close are included, installed switched off.

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:

TABBY_API_URL, TABBY_SECRET_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Tabby merchant account and its secret API key.

1. Sign in to the Tabby Merchant Dashboard (merchant.tabby.ai for the UAE, merchant.tabby.sa for Saudi Arabia), or ask your Tabby partner manager for the API keys.
2. Copy the secret key into TABBY_SECRET_KEY: sk_test_... for test payments, sk_... for live ones. The public key (pk_...) does not work here.
3. Set TABBY_API_URL to the API of your merchant region: https://api.tabby.ai for the UAE (and Kuwait), https://api.tabby.sa for Saudi Arabia. Tabby expects every call to go to the merchant's region. Test and live use the same address; the key decides.
4. Install the connector and run tabby_search_payments: it lists your latest payments and confirms the key.

Payment id and order number: a payment id is a UUID assigned by Tabby; your own order number is order.reference_id of the payment. To find a payment from an order number, the AI lists the payments of the order date with tabby_search_payments (created_from / created_to) and matches order.reference_id.

What it reads: your payments, newest first, with status, amount and currency, buyer (name, e-mail, phone), order reference and items, captures and refunds; one payment in full, with shipping address, tax, shipping, discount and every capture and refund with amounts and dates; checkout sessions, when a customer's checkout did not finish; customer disputes with reason, comment, attachments, disputed items and the days left before they are approved automatically; and the webhooks registered for a merchant code (the value of their header is not returned).

Payment status: AUTHORIZED means the customer approved and nothing is captured yet; CLOSED means captured in full or closed; REJECTED and EXPIRED mean no money moved. Without a status filter the search returns only AUTHORIZED and CLOSED payments.

Switched off at install: tabby_create_capture (captures an AUTHORIZED payment in full or in part when the order ships), tabby_create_refund (refunds a CLOSED payment; the money goes back to the customer at once and cannot be taken back) and tabby_close_payment (releases what is not captured, for a cancelled order or after a partial capture). They move money, so an administrator turns them on deliberately. Even then the AI shows you the payment, the amount and the currency and waits for your yes, and it passes a reference_id so a retry is not executed twice.

Amounts and times: amounts are strings with up to 2 decimals (AED, SAR) or 3 (KWD). Dates and times are UTC, ISO 8601.

Limits: the payment search returns at most 20 payments per call, and the AI pages with offset. The dispute list returns the 100 most recent disputes and pages with a token.

Common errors: 401 means a wrong secret key or a public key; 400 with an empty body can also be a missing key. 403 or 404 for a payment that exists usually means the wrong region in TABBY_API_URL. 409 on a refund means the payment is not refundable yet (not CLOSED) or the amount is too high.

The connector does not create checkout sessions, update payments, register webhooks or answer disputes; do those in the Tabby Merchant Dashboard.

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

• "Which Tabby payments were created yesterday, and which of them are still AUTHORIZED and not captured?"
• "Find the Tabby payment for our order number 100245 and show its captures and refunds."
• "List the open disputes and how many days are left on each before it is approved automatically."
• "A customer says the Tabby checkout did not finish: check this checkout session and tell me what happened."
• "Refund 120 AED on the Tabby payment of order 100245. Show me the payment and the amount first."

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