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. Listing the available tools works without authentication; executing a tool requires 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.
| Tool | Endpoint | Description |
|---|---|---|
getLatest | GET /v3/latest | Latest exchange rates |
getHistorical | GET /v3/historical | Historical exchange rates |
getConvert | GET /v3/convert | Convert a value between currencies |
getRange | GET /v3/range | Historical exchange rates for a time range |
getCurrencies | GET /v3/currencies | List supported currencies |
getCountries | GET /v3/countries | List countries |
getStatus | GET /v3/status | Account 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.