How to Connect BlockCypher to Microsoft Copilot via MCP

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

BlockCypher + Microsoft Copilot

Public blockchain data from BlockCypher for Bitcoin, Litecoin, Dogecoin, Dash and Ethereum: chain state and fee estimates, blocks, address balances, address transaction histories, single transactions and the mempool. Read-only, works without a token on the free tier.

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 required; BLOCKCYPHER_TOKEN is optional)

Step 1 — Set up the connector

Public data, token optional: setup takes under a minute. The connector reads public blockchain data from the BlockCypher API v1 (https://api.blockcypher.com/v1) for Bitcoin, Litecoin, Dogecoin, Dash and Ethereum. On the free tier BlockCypher answers these read-only calls without a token.

1. In the connector store, pick BlockCypher and install it. Leave BLOCKCYPHER_TOKEN empty for the free keyless tier.
2. Optional: sign up at https://accounts.blockcypher.com and copy the token from the dashboard into BLOCKCYPHER_TOKEN. It is sent as the token query parameter. blockcypher_get_transaction_confidence needs it, and with a paid plan it raises the limits.
3. Check it with blockcypher_get_chain and the network btc/main: it shows the current Bitcoin block height, the latest block and the fee estimates.

Networks: every tool takes network as coin/chain: btc/main, ltc/main, doge/main, dash/main, eth/main, or the test chains btc/test3, bcy/test and beth/test. Ethereum addresses are written without 0x.

What it reads: the state of a chain (height, latest block, unconfirmed transaction count and fee estimates per kB); blocks by hash or height, with their transaction hashes; the balance of an address (confirmed, unconfirmed and final); the history of an address, as light transaction references, as unspent outputs (UTXOs) or as complete transactions; single transactions with confirmations, fees, inputs and outputs; the confidence that an unconfirmed transaction will be confirmed; and the mempool, the latest transactions not yet in a block.

Amounts and times: amounts are always in the smallest unit. Bitcoin, Litecoin, Dogecoin and Dash have 100,000,000 units per coin (100,000,000 satoshi = 1 BTC), Ethereum has 10^18 wei per ether; the AI converts them before quoting an amount. Times are ISO 8601 in UTC. Confirmations are the chain height minus the block height plus 1.

Paging: address histories come newest first. While hasMore is true, the AI calls again with before set to the lowest block height it received; with after it fetches only what is new since a known height.

Read-only: every tool only reads, so there is nothing to confirm and no tool is switched off at install. Nothing is sent, signed or created.

Limits: the free tier allows 3 requests a second and 100 requests an hour, with or without a token, and 10 confidence lookups an hour. The hourly window resets at the top of the hour UTC, and blockcypher_get_chain shows how many calls are left. The AI prefers the balance call over the full address call and keeps page sizes small.

Common errors: 429 means the hourly or per-second limit is used up: wait until the next full hour (UTC) or use a paid token. 404 means an unknown address, hash or block on that network, often an address of another coin. 401 on the confidence call means the token is missing or wrong.

The connector does not send or sign transactions, manage wallets, register webhooks or read assets (OAP), and it does not cover Ethereum token (ERC-20) balances.

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 BlockCypher 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 current Bitcoin block height, and which fee per kB does BlockCypher suggest right now?"
• "Here is a Bitcoin address: what is its confirmed and unconfirmed balance in BTC?"
• "List the last 10 transactions of this Litecoin address with date, amount and confirmations."
• "How many confirmations does this transaction have, and what fee did it pay?"
• "Show me the unspent outputs (UTXOs) of this Dogecoin address and their total in DOGE."

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