Currency Exchange MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Currency Exchange MCP ServerWhat is the exchange rate between USD and 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 Exchange MCP Server
🛠️ Özellikler
🔄 Gerçek zamanlı döviz kuru sorgulama
🤖 AI model entegrasyonu
🛠️ MCP protokolü desteği
⚡ Modern uv dependency management
💱 ExchangeRate API entegrasyonu
Related MCP server: Realtime Exchange Rate MCP Server
Kurulum & Çalıştırma
Depoyu klonlayın:
git clone https://github.com/kullanıcı/MCP-Exchange.git
cd MCP-ExchangeBağımlılıkları yükleyin:
uv venv
source .venv/bin/activate # macOS/Linux
# veya
.venv\Scripts\activate # Windows
uv pip install .ExchangeRate API Anahtarınızı ayarlayın:
.env dosyasında EXCHANGE_API_KEY tanımlayın (API anahtarı ve belgelendirme için exchangerate-api.com sitesini kontrol edebilirsiniz).
EXCHANGE_API_KEY=YOUR_API_KEYSunucuyu çalıştırın:
Claude Desktop yapılandırma dosyasına (claude_desktop_config.json) manuel olarak ekleyin:
{
"mcpServers": {
"Exchange": {
"command": "uv",
"args": [
"run",
"--with",
"mcp[cli],requests,python-dotenv",
"mcp",
"run",
"/tam/yol/MCP-Exchange/main.py"
]
}
}
}💻 Claude Desktop ile Çalıştırma
Claude Desktop uygulaması açılır. "Exchange" seçeneği File > Settings > Developer sekmesinde ve sohbet ekranındaki ayarlarda görünmelidir.
Sohbet bölümünde "Exchange"e tıkladığımızda, main.py'de tanımlanan
get_exchange_ratearacı aktif olarak listelenir."Londra'da döviz kuru nedir?" sorusu sorulduğunda
get_exchange_rateişlemi başlar.Doğrulamadan sonra,
get_exchange_rateparametreleri ve dönüş sonucu ile yanıt döner.
📋 API Araçları
get_exchange_rate(base, target): İki para birimi arasındaki gerçek zamanlı döviz kuru bilgisi
💡 Örnek Kullanım
Kullanıcı: "USD TRY kuru nedir?"
AI: get_exchange_rate fonksiyonu otomatik tetiklenir
Sonuç: {"rate": 40.28, "base": "USD", "target": "TRY", "last_updated": "..."}🔧 Geliştirme
Python 3.13+
MCP Protocol
ExchangeRate API
Modern uv package manager
📄 Lisans
MIT License
Not: Normal döviz kuru uygulamalarından farklı olarak, kullanıcının manuel olarak döviz kuru bilgisini sorguladığı uygulamalardan farklı olarak, MCP-Exchange protokol tabanlı bir araç olarak çalışır. Döviz kuru verilerini JSON'da standartlaştırır ve MCP çerçevesi içinde çalışır. Claude Desktop gibi AI modelleri, kullanıcının sorusuna dayalı olarak manuel müdahale olmaksızın otomatik olarak tetikler. Bu da onu bağımsız bir döviz kuru uygulamasından ziyade sorunsuz entegre edilmiş bir backend hizmeti haline getirir.
Available Tools
1 toolget_exchange_rateC
Returns the current exchange rate from base to target currency.
| Name | Required | Description | Default |
|---|---|---|---|
| base | Yes | ||
| target | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description only states 'current' without detailing data freshness, update frequency, error behavior, or any limitations. It fails to disclose important behavioral traits beyond the basic function.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that directly conveys the tool's purpose with no extraneous words. It is front-loaded and efficiently communicates the core functionality.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with no output schema and no annotations, the description provides the essential purpose but lacks details on return format, error cases, or usage context. It is minimally complete for a straightforward retrieval operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, but the description adds the meaning of 'base' and 'target' as currencies. However, it does not provide format constraints, examples, or any guidance on valid values, leaving agents to guess or rely on external knowledge.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns an exchange rate from base to target currency, using a specific verb and resource. However, it could be more precise about the type of exchange rate (e.g., real-time vs. historical) but is sufficiently clear for basic usage.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, and there are no sibling tools to differentiate from. The description lacks context on prerequisites or appropriate scenarios for using this tool.
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 tool update
v0.1.0- First observed
get_exchange_rate
TDQS
Only one tool exists, so there is no possibility of ambiguity or overlap between tools.
With a single tool, naming consistency is not a meaningful dimension; the tool name 'get_exchange_rate' follows a clear verb_noun pattern.
A single tool for a currency exchange server is too few; users likely need conversion, listing of currencies, or historical rates, making the surface feel thin.
The tool only provides current exchange rates, missing essential operations like conversion, listing supported currencies, or historical data, leaving significant gaps.
Maintenance
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
Live & historical FX rates and currency conversion for AI agents. No API keys.
Live & historical FX rates and currency conversion for AI agents. No API keys.
51ExchangeRate MCP — wraps open.er-api.com (free, no auth)
Exchange MCP — wraps the Frankfurter currency exchange API (free, no auth)
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides current exchange rates for various currencies via the Model Context Protocol, allowing AI models to fetch real-time currency data.MIT
- AlicenseAqualityBmaintenanceProvides real-time foreign-exchange rates, historical data, and multi-currency lookups to MCP-compatible AI coding assistants like Claude Code and Cursor.4127MIT
- FlicenseNot gradedqualityCmaintenanceEnables currency conversion, exchange rates, geocoding, and weather queries through MCP tools, integrated with OpenAI Responses API.-
- FlicenseNot gradedqualityCmaintenanceAn 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.-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/EceDalpolat/MCP-Exchange'
If you have feedback or need assistance with the MCP directory API, please join our Discord server