Connect Orderful to Microsoft Copilot via MCP

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

Orderful + Microsoft Copilot

Orderful EDI platform: list and read EDI transactions (purchase orders, acknowledgments, ship notices, invoices, inventory advice) in both directions, read their message content, work an inbox of inbound deliveries, accept or fail deliveries, acknowledge transactions, send new transactions and list trading partner relationships.

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:

ORDERFUL_API_URL, ORDERFUL_API_KEY

Step 1 — Get credentials

1. Sign in at ui.orderful.com (US) or ui-eu.orderful.com (EU).
2. Click your avatar, then Settings → Organization Settings → API Credentials, and copy the API Token into ORDERFUL_API_KEY. It is sent in the orderful-api-key header.
3. Set ORDERFUL_API_URL to your region, without a trailing slash: https://api.orderful.com (US) or https://api-eu.orderful.com (EU). Data is not shared across regions; a US token does not work on the EU host.
4. Call orderful_get_organization to check the token and see your EDI accounts (ISA ids), then orderful_list_transactions, narrowed by direction, simplified_transaction_type (PURCHASE_ORDER, INVOICE, SHIP_NOTICE...), stream or business_number.

Receiving: read the Inbound Poller inbox with orderful_list_inbox_transactions (the inbox id is in the Orderful UI under Communication Channels), process each document, then call orderful_accept_delivery, or orderful_fail_delivery with a note. On JSON relationships also send orderful_acknowledge_transaction, once per transaction; X12 and EDIFACT relationships acknowledge with a 997 instead.

Sending: orderful_create_transaction posts an 850, 855, 856, 810, 846 or 860 in Orderful's Mosaic JSON. Use stream: test until the relationship is live: a live transaction goes to the trading partner. Check validationStatus on the result; INVALID transactions are not delivered.

Pagination: up to 100 transactions per page; for the next page, pass the nextCursor value from metadata.pagination.links.next.

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

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