Market MCP Server

Market MCP server exists for a simple reason — assistants are far more useful when they can act on Market directly instead of describing what you should do. Live & historical FX rates for AI agents, from European Central Bank data. No API keys.

What you get

Live and historical foreign-exchange rates for AI agents — as MCP tools your agent can call mid-task. No API keys.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Market is connected, these are the calls the assistant has available:

• fx_rates — Latest exchange rates for a base currency
• fx_convert — Convert an amount between two currencies at the latest ECB reference rate
• fx_historical — Exchange rates for a base currency on a specific past date
• fx_timeseries — Exchange-rate history over a date range, for trend analysis
• fx_currencies — Supported currencies and their names

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the market mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Market's toolset — fx_rates, fx_convert, fx_historical and 2 more — is a fair guide to whether it matches your workflow. It is maintained by com.datakoot; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.