How to Connect n11 to Microsoft Copilot via MCP

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

n11 + Microsoft Copilot

n11 seller integration API (Turkey): products with create, update, price and stock tasks and their results, category tree and attributes, orders as shipment packages with approval, splitting, pickup and invoice link, return requests and customer questions. Deleting products and refusing returns install 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:

N11_APP_KEY, N11_APP_SECRET

Step 1 — Get credentials

Setting up takes about 5 minutes. You need an n11 seller account.

1. Sign in to the n11 seller panel (so.n11.com) and open Hesabım > API Hesapları (account > API accounts). Create an API account if there is none.
2. Copy the API anahtarı (key) into N11_APP_KEY and the API şifresi (secret) into N11_APP_SECRET.
3. Install the connector and run n11_list_products: it lists your products and confirms the pair.

Which API: the n11 seller integration API on https://api.n11.com (documentation at developer.n11.com). Products, prices and stock, categories and orders use n11's current REST services, which take the key and secret in the appkey and appsecret headers. Returns, customer questions and the invoice link exist only on n11's SOAP services; there the connector puts the key and secret inside the request for you. Since 15 August 2025 the category services need the key as well.

What it reads: your products with n11 product id, stock code, title, category, product main id (group), status, sale status, prices, stock, VAT and commission rate, attributes and images, filtered by stock code, group code, sale or approval status, brand or category (productStatus InApproval means n11 waits for an action from you, CatalogRejected comes with rejectInfo); the whole category tree and the attributes of a leaf category with their allowed values; the results of product tasks; orders as shipment packages with order number, status, buyer, billing and shipping address, cargo company and tracking, agreed shipping date and the lines (orderLineId, product, stock code, quantity, price, discounts, sellerInvoiceAmount, commission); return requests with reason, order number, product, quantity, prices, buyer and cargo tracking, and the reasons you may give to postpone or refuse; customer questions with buyer, product, question and answer dates.

Every product write is a task: n11_create_products, n11_update_products (status Suspended takes a product off sale), n11_update_price_and_stock and n11_delete_products take up to 1,000 stock codes per call and answer with a task id and status IN_QUEUE (or REJECT with reasons). The AI then calls n11_get_task_details until the status is PROCESSED and reads each stock code's status (SUCCESS or FAIL) and reasons. A 200 on the write only means the task was queued. To create products the AI takes a leaf category (subCategories null) and sends every mandatory attribute: valueId when isCustomValue is false, customValue otherwise; the same productMainId groups variants.

Orders: new packages have status Created. n11_approve_order_lines moves lines to Picking; you ship with the n11 cargo campaign code in cargoTrackingNumber, then the package goes to Shipped and Delivered. A Picking package can be split by line (n11_split_package) or by quantity (n11_split_package_by_quantity, optionally cancelling quantities with reason 61 out of stock, 62 defective, 63 wrong price, 64 force majeure, 65 other). Bulky goods get a pickup with n11_create_collection_request, jewellery lines their labour cost with n11_send_labor_costs, and n11_send_invoice_link saves the invoice link (with invoice number and date for e-export orders, where micro is true).

Returns and questions: n11_list_claim_returns shows REQUESTED returns by default (ALL for every status; search by order number with searchInfoType ORDERID); n11_approve_claim_return refunds the buyer, n11_postpone_claim_return postpones the decision with a reason. n11_answer_product_question answers a question once; the answer is then public.

Writes: confirm first. Prices, stock, product status, order approval, splits and cancellations, returns and answers act on the live store. Before each call the AI shows you what changes (stock codes with old and new price or stock, lines, the answer text) and waits for your yes.

Switched off at install: n11_delete_products and n11_deny_claim_return. An administrator switches them on when the team needs them.

Data formats: order dates (startDate, endDate, lastModifiedDate, invoiceDateTime) are epoch milliseconds in Turkey time (UTC+3), e.g. 1793318400000; the SOAP services use dd/mm/yyyy. Without dates the package list shows the last 15 days, and longer windows are cut to 15 days. Prices are in TL unless currencyType says USD or EUR; prices go with a dot and two decimals, and salePrice may not exceed listPrice. Ids such as orderNumber and n11ProductId can grow longer over time, so treat them as strings. Order data before November 2024 is not available.

Paging: the REST lists start at page 0 and return totalPages; the AI stops when content is empty. Products come at most 250 per page, packages 100, returns 20.

Limits: the order list allows 1,000 requests a minute, product writes 1,000 stock codes per call, and the question list one call a minute.

Common errors: 401 (SellerApiUserUnauthorizedException) means n11 refused the key and secret: copy both again from Hesabım > API Hesapları. 403 Authentication failed means key and secret do not belong together or the API account is inactive. A SOAP answer with status failure carries n11's errorMessage. A task with REJECT or a stock code with FAIL lists the reasons, for example a missing mandatory attribute.

The connector does not create shipping labels and does not read your n11 payments and settlements: there are no tools for that.

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 n11 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 of our n11 products are in InApproval or CatalogRejected, and why?"
• "Set the stock of stock code ABC-1 to 40 and its sale price to 199.90 TL. Show me old and new values first, then check the task result."
• "List the new (Created) n11 packages of the last three days with their lines."
• "Show the open return requests on n11 and the reasons the buyers gave."
• "Draft answers to this week's open customer questions and let me approve each one before you send it."

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