
Wraps the open.er-api.com service to bring live currency conversion into your MCP workflow. Exposes a single tool, get_pair, for fetching the current exchange rate between two currencies. No API key required since it uses the free tier. Useful when you need real-time forex data in Claude without managing credentials or building your own integration. Part of the larger Pipeworx gateway, which bundles this with 600+ other data sources if you want broader access. The ask_pipeworx wrapper lets you query in natural language instead of calling tools directly. Runs over streamable HTTP transport.
ExchangeRate MCP — wraps open.er-api.com (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_rates | Get current exchange rates for a base currency (e.g., 'USD', 'EUR'). Returns conversion rates for all major currencies. Use when you need multiple rates at once. |
get_pair | Get the current exchange rate between two specific currencies (e.g., USD to EUR). Returns the conversion rate. Use for single currency pair lookups. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"exchangerate": {
"url": "https://gateway.pipeworx.io/exchangerate/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/exchangerate/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 Exchangerate data" })
The gateway picks the right tool and fills the arguments automatically.
MIT