Give AI agents live FX rates

Connect Claude, Cursor with FX tools.

Anonymous demo·10,000 calls/month with a free key·No credit card
claude code · remote HTTP
claude mcp add --transport http exchangerate-dev https://api.exchangerate.dev/v1/mcp/

Connect in one command, or use the local bridge

The remote endpoint is the fastest anonymous test. Keyed Desktop or Cursor setups run the npm stdio bridge.

Claude Code · remote HTTP

terminal
claude mcp add --transport http exchangerate-dev https://api.exchangerate.dev/v1/mcp/

Connects directly to https://api.exchangerate.dev/v1/mcp/. Anonymous calls use a shared IP-capped pool.

Claude Desktop or Cursor · stdio

mcp config · json
{
  "mcpServers": {
    "exchangerate-dev": {
      "command": "npx",
      "args": ["-y", "exchangerate-dev-mcp"],
      "env": {
        "EXCHANGERATE_API_KEY": "exr_live_..."
      }
    }
  }
}

Uses the maintained exchangerate-dev-mcp bridge. Replace exr_live_... with your API key.

Five tools, one FX contract

The MCP server calls the same domain logic as the REST API. Tool descriptions and schemas are served by exchangerate.dev, so the local bridge does not maintain a second copy.

ToolParametersUse it for
list_currenciesnoneDiscover supported currency codes, decimal precision, and derived-pair metadata.
get_ratebase, quote, date?Fetch a current or historical rate for one currency pair.
convertfrom, to, amountConvert an amount at the current indicative rate with currency-aware rounding.
get_rangebase, symbols, start_date, end_date, cursor?Retrieve a paginated daily time series for analysis or charting.
search_docsquery, limit?Search canonical API guidance before answering setup, pricing, or sourcing questions.

Freshness context travels with every rate

An agent should not repeat a number without knowing what it represents. Rate tools return source, market_session, and data_updated_at so the agent can distinguish an intraday observation from a daily reference and explain when the underlying data changed.

First-party schemas

The API operator maintains the endpoint and tool contract. The stdio package is a thin transport bridge, not a separate community wrapper.

One quota model

Each MCP tool call counts 1:1 against the same rate limit and monthly quota as a REST request. No hidden second meter.

Indicative by design

Responses are for software, analytics, research, and display, not settlement, executable pricing, or regulated trading.

Built for agent workflows, backed by the full API

The MCP surface covers 465 currency pairs, current and historical rates, amount conversion, and date ranges. Every plan receives the same data freshness and history; plans differ by throughput and monthly volume.

Read the API referenceRead the agent integration guideInspect the stdio bridge source

Questions agents and developers ask

What is the exchangerate.dev MCP server URL?

Claude Code and other remote-MCP clients can connect directly to the first-party Streamable HTTP endpoint at https://api.exchangerate.dev/v1/mcp/ without installing a local package.

Can I try the FX MCP server without an API key?

Yes for the remote HTTP endpoint — anonymous requests use a shared, IP-capped pool so you can test the real tools and data before signing up. The local stdio bridge requires EXCHANGERATE_API_KEY by default; set ALLOW_ANONYMOUS=true instead to run it keyless on the same anonymous pool. Use a free API key for attributed quota, a higher rate ceiling, and production use.

Do MCP tool calls count against the REST API quota?

Yes. Each MCP tool call counts as one API call against the same per-minute rate limit and monthly quota as the corresponding REST request.

Are the exchange rates suitable for trading or settlement?

No. The rates are indicative developer-grade references for software, analytics, research, and display. They are not executable quotes and must not be used for settlement or regulated trading.

Give your agent real FX tools

Try anonymously, then add a free key for attributed quota and production use.