How to Connect noon payments to Microsoft Copilot via MCP

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

noon payments + Microsoft Copilot

noon payments gateway (UAE, Saudi Arabia, Egypt): order status by order id or merchant reference with authorized, captured and refunded totals and transactions, scheduled settlement and commission reports, subscriptions and card tokens. Capture and refund 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:

NOON_PAYMENTS_API_URL, NOON_PAYMENTS_AUTH_KEY

Step 1 — Get credentials

Setting up takes about 5 minutes. You need access to the noon payments Merchant Portal.

1. In the Merchant Portal, open Account Settings > Applications. Create an application, or use an existing one, with only the roles it needs: Payment Integrator or Refund Manager for order lookups, Financial Auditor for reports, Token Manager for card tokens.
2. Build the key BusinessIdentifier.ApplicationIdentifier:ApplicationKey: the business identifier from the setup e-mail, a dot, the application identifier, a colon and the application key. Encode it in Base64, for example with printf '%s' 'mybusiness.myapp:KEY' | base64, and paste only the Base64 text into NOON_PAYMENTS_AUTH_KEY, without the word Key. The connector sends Authorization: Key <that text>.
3. Set NOON_PAYMENTS_API_URL to https://api.noonpayments.com (global, live) or https://api-test.noonpayments.com (test). The regional endpoints are https://api.sa.noonpayments.com and https://api.eg.noonpayments.com, with the test variants https://api-test.sa.noonpayments.com and https://api-test.eg.noonpayments.com. Only the endpoint, without /payment/v1. Keys differ per environment.
4. Install the connector and look up a recent order with noon_payments_get_order_by_reference and its shop order number to check the key.

Order id and order reference: order_id is the numeric order id noon returned when the payment was initiated, stored with the shop order (often as the payment transaction id). order_reference is your own reference sent at that moment, usually the shop order number. If several orders share a reference (retries), the newest is returned; the order id gives an exact match.

What it reads: an order by its id or by your reference, with its status (INITIATED, AUTHORIZED, CAPTURED, PARTIALLY_CAPTURED, REFUNDED, REVERSED, CANCELLED, FAILED, MARKED_FOR_REVIEW and others), amount and currency, the authorized, captured, refunded, reversed and remaining totals, the transactions (AUTHORIZATION, CAPTURE, REFUND and others, each with status, amount, time and id), the masked payment details and the next actions; the scheduled reports noon generated for a day or month, each with a time-limited link to download the ZIP (Excel or tab-separated); a recurring subscription with its creation date, status, validity, amount and schedule; and the masked card behind a saved card token (brand, masked number, expiry, holder name, status).

Reading an order: resultCode 0 only means the request worked, not that the payment succeeded. The AI judges by the order status and nextActions.

Reconciliation: ReconciliationSettlement is a daily report of the captures and refunds to reconcile with the bank settlement; ActiveSubscriptions, PaymentTokens, MerchantCommissions and MerchantCommissionDetails are monthly. For a day's settlement the AI lists the scheduled reports with report_type ReconciliationSettlement and that day, and you download the file from ReportUrl before the link expires. It does not loop over orders one by one for reconciliation, because noon throttles repeated polling.

Switched off at install: noon_payments_capture_order (captures an AUTHORIZED order in full or in part so the funds move to the merchant account) and noon_payments_refund_order (refunds a capture back to the customer's card, using the CAPTURE transaction id from the order; it cannot be undone and needs the Refund Manager role). Both move money, so an administrator turns them on deliberately. Even then the AI shows you the order, the amount and the currency and waits for your yes, and it passes a transaction_reference so a retry is not executed twice.

Limits: there is no endpoint to list or search orders, so the AI looks them up by id or reference, or uses the daily reports. Card token lookups are not meant for bulk runs.

Common errors: failures come back as HTTP 4xx or 5xx with resultCode, message and classDescription. Rejected_Unauthenticated means a wrong key or environment; Rejected_AccessDenied (or 403) means the application lacks the role for that call; Invalid_BadRequest points to a parameter. 404 usually means a NOON_PAYMENTS_API_URL with a path, or an order that does not exist in this environment. 429 means throttling: the AI waits before retrying and does not repeat the same failing request, because noon may lock the order or ban the address.

The connector does not initiate payments, authorize, reverse or cancel orders, or handle fraud review.

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 noon payments 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

• "What is the status of the noon payments order for our shop order 100245, and how much of it is captured and refunded?"
• "Was order 3108459210 captured in full, or is an amount still remaining?"
• "Get yesterday's ReconciliationSettlement report from noon payments and give me the download link."
• "Look up this subscription and tell me its status, amount and schedule."
• "Refund 75 AED of the capture on order 3108459210. Show me the order 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