
Wraps the Frankfurter API to give Claude currency exchange capabilities without authentication. Exposes three tools: get_rate for checking exchange rates between currency pairs, convert for calculating amounts across currencies, and get_currencies to list all supported codes. Useful when you need quick forex data in conversations without managing API keys or rate limits. Part of the Pipeworx gateway ecosystem, so you can add it standalone or bundle it with their 250+ data source collection. Returns timestamps with rates and handles the usual suspects like USD, EUR, GBP plus a longer tail of currencies.
Exchange MCP — wraps the Frankfurter currency exchange API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_rate | Get the current exchange rate between two currencies (e.g., USD, EUR). Returns the rate value and timestamp. |
convert | Convert an amount from one currency to another at current rates. Returns the converted amount and the exchange rate applied. |
get_historical_rate | Get the exchange rate between two currencies on a specific date (format: YYYY-MM-DD). Returns the historical rate and date. |
get_currencies | List all supported currencies with codes and full names. Use to verify currency codes before converting or checking rates. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"exchange": {
"url": "https://gateway.pipeworx.io/exchange/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/exchange/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Exchange data" })
The gateway picks the right tool and fills the arguments automatically.
MIT