Skip to main content
Glama
sin4ch

Exchange Rate MCP Server

by sin4ch
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Exchange Rate MCP Server

A Model Context Protocol (MCP) server that provides currency conversion functionality using the ExchangeRate-API.

Features

  • Convert amounts between different currencies using real-time exchange rates

  • Support for about 161 currencies currently

  • Error handling for invalid currency codes, API errors, and network issues

Related MCP server: FX Currency MCP Server

Setup

Prerequisites

  • Python 3.12+

  • uv package manager

  • ExchangeRate-API key (free tier available)

Installation

  1. Clone this repository

  2. Install dependencies:

    uv sync

  3. Copy the .env.example file into your .env:

    cp .env.example .env

  4. Replace your_api_key in the .env with your actual API key.

    You can get your free API key from ExchangeRate-API

Configuration

Copy and paste this in the claude_desktop_config.json file:

{
  "mcpServers": {
    "exchange-rate-mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/exchange-rate-mcp",
        "run",
        "main.py"
      ]
    }
  }
}

Usage

Once configured, you can use the convert_currency tool in Claude to convert between currencies:

  • convert_currency(100, "USD", "EUR") - Convert 100 USD to EUR

  • convert_currency(50, "GBP", "JPY") - Convert 50 GBP to JPY

Troubleshooting

  • "uv: command not found": Make sure uv is installed and the full path is specified in the configuration

  • "Invalid API key": Check that your .env file contains a valid ExchangeRate-API key

Available Tools

1 tool
convert_currencyB

Convert an amount from one currency to another using current exchange rates.

ParametersJSON Schema
NameRequiredDescriptionDefault
amountYes
base_currYes
target_currYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'using current exchange rates,' which hints at real-time data, but fails to specify source reliability, rate limits, error handling, or whether the operation is read-only or has side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It is appropriately sized and front-loaded, efficiently conveying the core function without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (3 parameters, no annotations, but with an output schema), the description is minimally adequate. The output schema likely covers return values, but the description lacks details on exchange rate sources, accuracy, or operational constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It implies parameters for amount and currencies but does not detail their semantics (e.g., currency codes, numeric formats). The description adds minimal value beyond the schema's structural definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: converting an amount between currencies using current exchange rates. It specifies the verb ('convert') and resource ('currency'), making the function unambiguous. However, with no sibling tools, it cannot demonstrate differentiation from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. It simply states what the tool does without context about timing, limitations, or comparison to other methods.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedconvert_currency
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'convert_currency' follows a clear verb_noun pattern.

Tool Count2/5

A single tool for an exchange rate server feels thin and limited in scope. While it covers the core conversion functionality, it lacks supporting operations like fetching available currencies, historical rates, or batch conversions, which are typical for such domains.

Completeness2/5

The tool surface is severely incomplete for an exchange rate domain. It only provides currency conversion, missing essential features like listing supported currencies, retrieving exchange rate data, or handling historical queries, which are common in financial APIs.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Frankfurter MCP

    jessicayanwang
    A
    license
    A
    quality
    D
    maintenance
    Provides access to currency exchange rates and conversion tools using the Frankfurter API, including latest rates, historical data, and time series from sources like the European Central Bank.
    5
    MIT

  • FX Currency MCP Server

    pavm035
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides real-time and historical foreign exchange rates for 31+ currencies, enabling currency conversion, historical rate lookups, and time series analysis using data from the Frankfurter API.
    -

  • exchangerate

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides real-time exchange rates for any currency pair using open.er-api.com, simplifying currency conversion with a single tool.
    14
    MIT

  • realtime-currency-exchange-mcp

    Ethereal-Jay
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables real-time currency exchange rate lookup, conversion, historical rates, and currency catalog using the free Frankfurter API, no API key required.
    8
    ISC

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sin4ch/exchange-rate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server