MCP Server

currencyapi ships a hosted Model Context Protocol (MCP) server, so AI agents and assistants can call the API as native tools — no SDK or glue code required.

https://api.currencyapi.com/mcp

The endpoint speaks the streamable HTTP transport. All requests — including listing the available tools — require your API key, sent as the apikey header. You can get a free API key here.

Connect

Using Claude Code:

claude mcp add --transport http currencyapi https://api.currencyapi.com/mcp --header "apikey: YOUR_API_KEY"

Or add the server to any MCP-capable client (Claude Desktop, Cursor, VS Code, ...):

{
  "mcpServers": {
    "currencyapi": {
      "url": "https://api.currencyapi.com/mcp",
      "headers": { "apikey": "YOUR_API_KEY" }
    }
  }
}

Available tools

The tools are generated from the same OpenAPI specification that describes the REST API, so they always match the documented endpoints, parameters and responses.

ToolEndpointDescription
getLatestGET /v3/latestLatest exchange rates
getHistoricalGET /v3/historicalHistorical exchange rates
getConvertGET /v3/convertConvert a value between currencies
getRangeGET /v3/rangeHistorical exchange rates for a time range
getFluctuationGET /v3/fluctuationHow rates changed between two dates
getAverageGET /v3/averageAverage, low and high rates per month, quarter or year
getOfficialGET /v3/officialOfficial central bank exchange rates
getOfficialRangeGET /v3/official/rangeOfficial central bank exchange rates for a date range
getOfficialSourcesGET /v3/official/sourcesList central bank sources
getCurrenciesGET /v3/currenciesList supported currencies
getCountriesGET /v3/countriesList countries
getStatusGET /v3/statusAccount quota status

Quotas and errors

Tool calls are metered exactly like REST requests: they consume your plan quota and return the same status codes and error responses (401, 422, 429, ...). If a call fails, the tool result contains the API's error message including hints on how to proceed.