Connect Falabella to Microsoft Copilot via MCP

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

Falabella Seller Center + Microsoft Copilot

Let your AI run your falabella.com store in Chile, Colombia or Peru through Falabella Seller Center: products, stock per warehouse, brands, categories and their attributes, orders and their items, shipping labels and feed results, plus creating products and changing prices, stock and images.

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:

FALABELLA_USER_ID, FALABELLA_API_KEY, FALABELLA_SELLER_ID, FALABELLA_BUSINESS_UNIT

Step 1 — Get credentials

Setting up takes about 5 minutes. You need a seller account on Falabella Seller Center, a Seller Center user with an API role, that user's API key and your Seller ID.

There is no sandbox: every call, writes included, acts on your live store.

1. Sign in at sellercenter.falabella.com with the user the connector should act as. An administrator can add a dedicated user under Mi cuenta → Usuarios → Agregar Usuario.
2. Open Mi cuenta → Usuarios. Put the user's e-mail address into FALABELLA_USER_ID and the value in that row's API Key column into FALABELLA_API_KEY.
3. Give the user an API role: Seller API Access (every method), Seller API Product Access (products, brands, categories, images and feeds) or Seller API Order Access (orders). A method outside the role answers E009: Access Denied.
4. Copy your Seller ID, shown under Mi cuenta, into FALABELLA_SELLER_ID.
5. Set FALABELLA_BUSINESS_UNIT to your country: FACL Chile, FACO Colombia, FAPE Peru. One connector serves one country; add a second connector for another.
6. Install the connector. Run falabella_seller_center_feed_count to check the connection: it is a light call.

How it signs: every request is signed with HMAC-SHA256, keyed with your API key. The key itself is never sent. A request whose timestamp is too far off is refused (E003).

Cloud and self-hosted work the same way: the credentials are the same, and there is no redirect URL to set.

Where to start: falabella_seller_center_get_products lists products with filters for status, search, SKUs and dates. falabella_seller_center_get_stock shows stock per warehouse, Fulfillment by Falabella included. For orders, falabella_seller_center_get_orders and falabella_seller_center_get_order_items, which return the OrderItemId and PackageId that labels and status changes need. falabella_seller_center_get_document returns the shipping label.

New products: find the category with falabella_seller_center_get_category_suggestion from a title, or in falabella_seller_center_get_category_tree (products go in leaf categories only). Read its attributes with falabella_seller_center_get_category_attributes and the exact brand name with falabella_seller_center_get_brands. Then create the products with falabella_seller_center_create_products and add images with falabella_seller_center_set_images.

Writes are feeds: creating, updating, pricing, stocking, imaging and removing products is asynchronous. A successful answer only means the request was accepted. falabella_seller_center_feed_status shows the outcome: wait until Status is Finished, Error or Canceled, then read FailedRecords and FeedErrors, because a feed can finish with some records rejected. Falabella allows 50 feed calls freely, then one every 2 minutes per seller, so the AI puts several products into one request instead of one call per SKU.

Country codes: the business unit is upper case (FACL). Inside product XML the same country is the OperatorCode in lower case: facl, faco, fape.

Switched off at install: falabella_seller_center_remove_products (remove products), falabella_seller_center_set_status_ready_to_ship (mark order items ready to ship) and falabella_seller_center_set_status_canceled (cancel an order item). Switch them on on the connector page when the AI should use them; the AI asks you to confirm every call. Creating and updating products and changing prices, stock and images is switched on (falabella_seller_center_create_products, falabella_seller_center_update_products, falabella_seller_center_update_price, falabella_seller_center_update_stock, falabella_seller_center_update_stock_xml, falabella_seller_center_set_images).

Formats: date filters are ISO 8601 (2026-11-01T00:00:00+00:00). Prices use a dot as decimal separator. Id lists go in brackets: [123456,123457]. An update only changes the elements it contains.

Common errors: E007 means the signature did not match: the API key must belong to the user in FALABELLA_USER_ID (same row under Mi cuenta → Usuarios), copied whole. E009 means the user's role does not cover that method. E429 means the feed limit was reached: wait and try again. Falabella reports refusals with HTTP 200; the connector reports them as failed calls.

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 Falabella Seller Center 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 orders came in today, and which items still need to ship?"
• "Show the stock of SKU ZAP-RUN-42 in each warehouse."
• "Did my last feed finish? List any rejected records and why."
• "Change the price of SKU ZAP-RUN-42 to 49990 with a sale price of 39990 until the end of the month."
• "Suggest a category for 'Zapatillas running hombre' and list its mandatory attributes."

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