How to Connect Binance to Microsoft Copilot via MCP

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

Binance + Microsoft Copilot

Let your AI read live crypto market data from Binance: spot prices and 24 hour changes of every pair, order books, recent trades and price history, and for USD-M futures the mark price, funding rates, open interest and long/short ratio. Public data, no account or key needed. Read-only: it cannot trade or move funds.

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:

(none: public data, no API key)

Step 1 — Set up the connector

Public market data, no key: there is nothing to set up. The connector reads Binance's public market data from the Spot API and the USD-M futures API. No Binance account, API key or sign-in is needed.

1. In the connector store, pick Binance and install it. There is nothing to paste and no Authorize with Provider step.
2. Check it with binance_get_server_time: if Binance answers, it serves the region your server calls from. Then ask for a price: binance_get_price with BTCUSDT tells you what one bitcoin costs in Tether right now.

Where it works: Binance refuses requests from the United States and some other restricted regions with HTTP 451. AnythingMCP Cloud calls Binance from the EU, so it works there. A self-hosted server in a restricted region gets 451 on every tool. For spot data only, a self-hosted server may point the connector's base URL at Binance's market-data mirror https://data-api.binance.vision, which serves the same spot routes; the futures tools always call fapi.binance.com. Binance.US is a different exchange with its own prices and is not covered.

It cannot trade or move funds, by design: no tool places or cancels an order, buys, sells or converts, or transfers, deposits or withdraws anything, and none can be switched on, because the connector never signs a request and never sees a Binance account. It cannot see anyone's balances, orders, positions, trades or deposit addresses either. For your own account, use the Binance app or website.

Not financial advice: prices, volumes, funding rates and ratios are information. The AI does not tell you to buy, sell, hold, go long or go short. It shows the numbers with their time and source, and reminds you that crypto prices move fast and that leveraged futures can lose more than the margin.

What it reads: on spot, the price of one pair, several or all, 24 hour statistics and rolling windows from 1 minute to 7 days, the best bid and ask, order books, recent trades, candles and a pair's trading rules such as tick size and minimum order value. On USD-M futures, the last price, 24 hour statistics, candles, order books, the mark and index price with the current funding rate and the next funding time, past funding rates, open interest and its history, and the long/short account ratio. The futures list also includes perpetuals on stocks and commodities and quarterly delivery contracts.

Valuing holdings you name: tell the AI what you hold, for example 0.5 BTC and 3 ETH. It multiplies each amount by the spot price in a quote asset you use (BTCEUR, ETHEUR or the USDT pairs) and adds them up, stating the time of the prices. USDT and USDC are dollar stablecoins, close to but not exactly 1 USD.

Symbols: Binance writes a pair as one word in capitals, base asset first: BTCUSDT (bitcoin priced in Tether), ETHBTC, BNBEUR. There is no dash and no slash. Many pairs do not exist (there is BTCEUR but no SOLCHF), and an unknown one answers 400 with code -1121. Spot and futures are separate markets with their own prices: BTCUSDT on futures is the perpetual contract, not the spot pair.

Numbers and times: prices come as text so no digit is lost. Times are Unix milliseconds in UTC, and the AI converts them to your time zone. Funding rates are fractions per funding interval (0.0001 is 0.01 %), and a positive rate means longs pay shorts. The long/short ratio counts accounts, not position size. Open interest history and the long/short ratio only go back 30 days.

Limits: Binance limits each IP address by request weight: 6,000 a minute on spot and 2,400 on futures, plus 1,000 requests per 5 minutes for the futures statistics and 500 for funding history. A Cloud server shares one IP among its users, so the AI asks for several symbols in one call and keeps results small. After a 429 it stops and waits; continuing gets the IP banned with HTTP 418 for 2 minutes up to 3 days.

Common errors: 400 with code -1121 is an unknown symbol, -1100 or -1102 a malformed or missing parameter. 451 means Binance does not serve the server's region. 403 means Binance's firewall blocked the request, usually a rate limit. 429 and 418 mean wait.

The connector does not cover anything that needs a Binance account or a signed request (balances, orders, trades, positions, leverage, transfers, deposits, withdrawals, Earn, Convert, margin), COIN-M futures, options, WebSocket streams or Binance.US.

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 Binance 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 do Bitcoin, Ether and Solana cost in USDT right now, and how did they move in the last 24 hours?"
• "I hold 0.5 BTC and 3 ETH. What are they worth in euros right now?"
• "What is the funding rate on the BTCUSDT perpetual right now, and how has it changed over the last week?"
• "Which futures contracts have the most extreme funding rates at the moment?"
• "Show me open interest and the long/short ratio for ETHUSDT over the last 7 days, day by day."

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