Connect FXMacroData to Microsoft Copilot via MCP

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

FXMacroData + Microsoft Copilot

Official macroeconomic releases, central-bank policy rates, release calendars and FX rates for 22 currencies via the FXMacroData API. 5 read-only tools; the data catalogue, the USD calendar and recent USD releases work without an API key.

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

Step 1 — Get credentials

No key is needed to start. Without one, the API serves the data catalogue for every currency, the USD release calendar and USD releases from the last 90 days, each readable 15 minutes after publication. Keyless use has a fair-use allowance of 100 requests a day.

1. Install the connector and call fxmacrodata_data_catalogue with a lowercase currency code (for example usd) to get the indicator slugs, such as inflation, policy_rate or unemployment.
2. Use those slugs with fxmacrodata_latest_announcements, fxmacrodata_indicator_history and fxmacrodata_release_calendar.
3. For other currencies, FX rates, full history and real-time releases, subscribe at https://fxmacrodata.com/subscribe and set the optional FXMACRODATA_API_KEY (sent as the X-API-Key header). fxmacrodata_fx_rates always needs it.

A route that needs a key answers 401 api_key_required: the data exists behind a subscription, it is not missing. A wrong key answers 401 invalid_api_key, even on the free routes. In the answers, date is the reference period (the month, for CPI), not the release day; the release time is announcement_datetime (Unix seconds, UTC). Lists return 20 rows by default and up to 100 with limit.

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