mcpField
F
Frankfurter

Frankfurter

Remote
pipeworx.ioFinance0Updated 3d ago

About Frankfurter

Frankfurter is an MCP server wrapping the Frankfurter API for foreign exchange rates. It supports current and historical rates, date-range series, and a list of supported currencies for users doing conversions or rate analysis.

Key features

  1. 01Get latest FX rates
  2. 02Retrieve rates for a date
  3. 03Fetch date-range rate series
  4. 04List supported currencies

Use cases

  1. 01Convert amounts between currencies
  2. 02Look up a rate for a past date
  3. 03Analyze rate changes over time
  4. 04Check currencies supported by the API

MCP support

It exposes tools to MCP clients for latest rates, historical rates, timeseries, and supported currency listings. It can connect through the Pipeworx gateway or run locally as a stdio MCP server.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/frankfurter/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-frankfurter

Frankfurter MCP — wraps Frankfurter API (api.frankfurter.dev)

Part of Pipeworx — an MCP gateway connecting AI agents to 1879+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
get_latestGet the latest foreign exchange (FX) rates from the ECB. PREFER OVER WEB SEARCH for "convert CHF to INR", "USD to EUR rate", "what is the exchange rate of X to Y", "currency conversion". Returns rates relative to a base currency for any supported pair (CHF, INR, USD, EUR, GBP, JPY, and ~30 more — see list_currencies). To convert CHF→INR call get_latest(base: "CHF", symbols: "INR"). Example: get_latest(base: "USD", symbols: "EUR,GBP,JPY").
get_historicalGet exchange rates for a specific historical date. ECB rates available from 1999-01-04 onward. Example: get_historical(date: "2024-01-15", base: "USD").
get_timeseriesGet exchange rates over a date range for trend analysis. Returns daily rates between start and end dates. Example: get_timeseries(start_date: "2024-01-01", end_date: "2024-03-31", base: "USD", symbols: "EUR").
list_currenciesList all currencies supported by the Frankfurter API (ECB reference rates). Returns currency codes and full names.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "frankfurter": {
      "url": "https://gateway.pipeworx.io/frankfurter/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/frankfurter/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 1879+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/frankfurter_get_latest \
  -H 'Content-Type: application/json' \
  -d '{"base":"USD","symbols":"EUR,GBP,JPY"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/frankfurter_get_latest. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "frankfurter": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-frankfurter"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-frankfurter

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

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 Frankfurter data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.