How to Connect Zerion to Microsoft Copilot via MCP

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

Zerion + Microsoft Copilot

Onchain wallet data from Zerion for EVM chains and Solana: portfolio value, token and DeFi positions, decoded transaction history, profit and loss, balance charts, NFTs, token prices and charts, chains and gas prices. Read-only; a free developer key is enough to start.

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:

ZERION_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Zerion API key; a free developer plan exists.

1. Sign up at https://dashboard.zerion.io and create an API key.
2. Paste the key into ZERION_API_KEY. Zerion takes it as HTTP Basic auth, with the key as user name and an empty password; the connector builds that header, so paste only the key, without a Basic prefix.
3. Install the connector and run zerion_list_chains: it lists the supported chains and confirms the key.

Addresses: the wallet tools take an EVM address (0x...) or a Solana address. ENS names are not resolved. The NFT tools work on EVM wallets only. Any public address can be read; no wallet is connected and nothing is signed.

What it reads:

• Portfolio: the total value of a wallet across chains, split by position type (wallet, deposited, borrowed, locked, staked) and by chain, with the change over 24 hours.
• Positions: every token with chain, quantity, price, value and 24 hour change, highest value first. With positions: no_filter DeFi positions such as lending, staking and liquidity are included, with protocol and dapp; only_complex returns DeFi positions only. Spam tokens are left out by default.
• Transactions: the decoded history, newest first, with hash, chain, time, operation type (send, receive, trade, deposit, withdraw, approve, mint, ...), status, fee, every transfer with token, direction, quantity and value, and the dapp. Filters by chain, operation type, token, asset type (fungible or NFT), time window or a text search.
• Profit and loss (FIFO): realized and unrealized gain, total gain, net invested, cost basis, fees and relative gains in percent, optionally for some chains or tokens or for sales in a time window.
• The balance of a wallet over time, for a period from hour up to max.
• NFTs: the NFTs of a wallet with collection, media and floor price, its collections with counts and total floor price, and the total NFT value.
• Tokens: search by name or symbol, with price, market cap, supply, price changes over 1, 30, 90 and 365 days, volume and the contract on each chain; a token by chain and contract address; price charts with first, min, average, max and last.
• Chains with the data each supports, and current gas prices per chain and speed.

Data formats: answers follow JSON:API: data holds the items, each with id, attributes and relationships (chain and token ids). Quantities come as quantity.float in human units next to the raw integer. Values and prices are in the requested currency (USD by default; also EUR, GBP, CHF, JPY, ETH, BTC and others). mined_at and updated_at are ISO 8601; chart points are [unix_seconds, value]; time filters such as min_mined_at and since take Unix milliseconds. Filters with several values are comma-separated without spaces, for example chain_ids: ethereum,base,arbitrum.

Paging: list tools return links.next when more items exist. The AI passes its page[after] value as page_after and stops when links.next is missing. Transactions come in pages of up to 100.

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

Limits: requests per second, per day and per month depend on the plan; the free Developer plan allows 2,000 requests a day at 3 per second. DeFi positions (only_complex or no_filter), wallet charts and PnL count toward an advanced quota of 25% of the monthly requests; when it is used up only those calls answer 429 and the others keep working. The NFT tools may first answer 202 while a wallet's NFTs are being indexed: ask again a few seconds later.

Common errors: 401 means a wrong key. 400 means an invalid address or filter; PnL and transactions also refuse token contract and exchange hot-wallet addresses. 429 means a rate limit or the quota.

The connector does not sign or send transactions, swap tokens, subscribe to webhooks or manage wallet sets.

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 Zerion 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 wallet 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 worth right now, and how is it split across chains?"
• "List the DeFi positions of this wallet, such as lending, staking and liquidity, with protocol and value."
• "Show the trades this wallet made on Base in the last 30 days, with tokens and USD values."
• "What are the realized and unrealized gains of this wallet on Ethereum this year, and how much did it pay in fees?"
• "Find the PEPE token and show its price over the last month with the low, average and high."

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