How do I use Currency Converter MCP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Currency Converter MCP convert 500 USD to EUR" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Currency Converter MCP

by wesbos

Overview Schema Related Servers Score Discussions

TypeScript

Remote

MCP Currency Converter Server

An MCP server that provides real-time currency conversion and exchange rate data using the Frankfurter API.

Using

URL base is https://currency-mcp.wesbos.com

There are two endpoints - /mcp for streamable HTTP and /sse for legacy HTTP+SSE.

Right now many clients do not offer support for streamable http, so you can use it with a proxy:

{
  "mcpServers": {
    "currency-conversion": {
      "command": "npx",
      "args": ["mcp-remote", "https://currency-mcp.wesbos.com/sse"]
    }
  },
}

Related MCP server: Frankfurter Forex MCP

Available Tools

`convert_currency`

Convert an amount from one currency to another.

Parameters:

from (string): Source currency code (3 letters, e.g., "USD", "EUR")
to (string): Target currency code (3 letters, e.g., "USD", "EUR")
amount (number): Amount to convert (positive number)

Example: Convert 100 USD to EUR

{
  "from": "USD",
  "to": "EUR",
  "amount": 100
}

`get_latest_rates`

Fetch the latest exchange rates.

Parameters:

base (string, optional): Base currency code (defaults to EUR)
symbols (string, optional): Comma-separated currency codes to limit results

Example: Get USD rates for specific currencies

{
  "base": "USD",
  "symbols": "EUR,GBP,JPY"
}

`get_currencies`

List all available currencies with their full names.

Parameters: None

`get_historical_rates`

Get historical exchange rates for a specific date.

Parameters:

date (string): Date in YYYY-MM-DD format
base (string, optional): Base currency code (defaults to EUR)
symbols (string, optional): Comma-separated currency codes to limit results

Example: Get historical EUR rates for January 1, 2024

{
  "date": "2024-01-01",
  "base": "EUR",
  "symbols": "USD,GBP"
}

Data Source

Exchange rate data is provided by the Frankfurter API

Available Tools

4 tools

convert_currencyD

ParametersJSON Schema

Name	Required	Description
`from`	Yes	Source currency code (e.g., USD, EUR)
`to`	Yes	Target currency code (e.g., USD, EUR)
`amount`	Yes	Amount to convert

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

get_currenciesD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

get_historical_ratesD

ParametersJSON Schema

Name	Required	Description
`date`	Yes	Date in YYYY-MM-DD format
`base`	No	Base currency code (default: EUR)
`symbols`	No	Comma-separated currency codes to limit results

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

get_latest_ratesD

ParametersJSON Schema

Name	Required	Description	Default
`base`	No	Base currency code (default: EUR)
`symbols`	No	Comma-separated currency codes to limit results (e.g., USD,GBP,JPY)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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.

4 tool updatesAug 15, 2025
- First observedconvert_currency
- First observedget_currencies
- First observedget_historical_rates
- First observedget_latest_rates

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.2/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: convert_currency performs conversions, get_currencies lists available currencies, get_historical_rates retrieves past rates, and get_latest_rates provides current rates. The names alone make their functions unambiguous.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., convert_currency, get_currencies). There are no deviations in style or convention, making the set predictable and easy to parse.

Tool Count5/5

With 4 tools, this server is well-scoped for a currency converter domain. Each tool serves a distinct and essential function, covering core operations without bloat or unnecessary complexity.

Completeness5/5

The tool set provides complete coverage for currency conversion workflows: listing currencies, getting latest rates, accessing historical data, and performing conversions. There are no obvious gaps for the stated purpose.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

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

Related MCP Connectors

anirbanbasu-frankfurtermcpOAuth
ai.smithery
A MCP server for the Frankfurter API for currency exchange rates.
Finance Open Data Search
26
Frankfurter A
io.github.pipeworx-io
Frankfurter MCP — wraps Frankfurter API (api.frankfurter.dev)
Finance Open Data
352
Currency Converter Mcp
io.github.varvararatta
MCP server for currency_converter_mcp
Finance
2
exchange A
io.github.pipeworx-io
Exchange MCP — wraps the Frankfurter currency exchange API (free, no auth)
Finance Search
352

Related MCP Servers

FrankfurterMCP
Finance Search
anirbanbasu
A
license
B
quality
A
maintenance
A MCP server for the Frankfurter API for currency exchange rates.
Updated 2 months ago (2026-07-20 06:54 UTC)
6
6
MIT
Frankfurter Forex MCP
Finance Search Open Data
lcfranca
F
license
B
quality
D
maintenance
An MCP server that provides currency rates, conversions, and historical exchange-rate data using the Frankfurter API. It enables users to retrieve latest rates, convert amounts between currencies, and access time-series data for currency pairs.
Updated 6 months ago (2026-02-25 00:17 UTC)
3
-
plinth-fx-mcp
plinthkit
-
license
Not graded
quality
Not graded
maintenance
MCP server that provides real exchange-rate data from the European Central Bank, including latest rates, currency conversion, historical rates, and time series.
Updated 3 months ago (2026-05-30 01:50 UTC)
-
Monedas y Clima MCP Server
Finance Weather Services Location Services
leireee08
F
license
Not graded
quality
C
maintenance
An MCP server that integrates ExchangeRate-API and Open-Meteo to provide currency conversion and weather tools, enabling natural language queries for exchange rates, weather, and geocoding.
Updated 2 months ago (2026-07-12 13:45 UTC)
-

Appeared in Searches

A server for planning travel itineraries and trips

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/wesbos/currency-conversion-mcp'

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