MCP server for real-time currency exchange rates and crypto prices. Convert between 60+ fiat currencies and 30+ cryptocurrencies with multi-source
Currency Exchange MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Currency Exchange MCP directly instead of describing what you should do. MCP server for real-time currency exchange rates and crypto prices. Convert between 60+ fiat currencies and 30+ cryptocurrencies with multi-source fallback.
A currency exchange MCP server for real-time forex rates and cryptocurrency prices via the Model Context Protocol. Convert between 60+ fiat currencies and 30+ cryptocurrencies — with multi-source failover, smart currency resolution, batch conversion, and historical rate lookups. No API keys needed for upstream data sources.
Once Currency Exchange MCP is connected, these are the calls the assistant has available:
convert_currency — Convert an amount between any supported fiat or cryptocurrency pairbatch_convert — Convert an amount from one currency to multiple targets in a single call. More cost-effective than multiple individual conversionsget_exchange_rates — Get current exchange rates for a base currency against multiple targetsget_historical_rate — Get historical exchange rates for a single date or a date range (max 365 days)You will need one environment variable: YOUR_APIFY_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Currency Exchange MCP's toolset — convert_currency, batch_convert, get_exchange_rates and 1 more — is a fair guide to whether it matches your workflow. It is maintained by ruddxxy; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| convert_currency | Convert an amount between any supported fiat or cryptocurrency pair. |
| batch_convert | Convert an amount from one currency to multiple targets in a single call. More cost-effective than multiple individual conversions. |
| get_exchange_rates | Get current exchange rates for a base currency against multiple targets. |
| get_historical_rate | Get historical exchange rates for a single date or a date range (max 365 days). |
{
"mcpServers": {
"currency-exchange": {
"url": "https://vector384--currency-exchange-mcp.apify.actor/mcp",
"headers": {
"Authorization": "Bearer YOUR_APIFY_API_TOKEN"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| YOUR_APIFY_API_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.