Bnr Ro
National Bank of Romania (Banca Naţională a României, BNR) FX reference rates MCP. Keyless.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http bnr-ro 'https://gateway.pipeworx.io/bnr-ro/mcp'
{
"mcpServers": {
"bnr-ro": {
"type": "http",
"url": "https://gateway.pipeworx.io/bnr-ro/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-bnr-ro
National Bank of Romania (Banca Naţională a României, BNR) FX reference rates MCP. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
bnr_exchange_rates | Latest National Bank of Romania (BNR) official FX reference rates, parsed from BNR's daily XML feed. Returns the reference date plus an array of currency rates. Each rate is RON (Romanian leu) per multiplier units of the currency (multiplier is 1 unless noted, e.g. 100 for HUF/JPY/KRW), so the per-1-unit rate = value / multiplier. Currencies are ISO 4217 codes (plus XAU gold, XDR SDR). |
bnr_exchange_rates_history | Historical National Bank of Romania (BNR) official FX reference rates, parsed from XML. With no arguments (or period="10days") returns the last 10 published business days. Pass year=YYYY (e.g. 2024) to return every published day in that calendar year. Returns an array of daily entries, each { date, rates:[{currency, value, multiplier}] }. Each rate is RON per multiplier units of the currency; per-1-unit rate = value / multiplier. Currencies are ISO 4217 codes. Note the currency set can vary across dates. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bnr-ro": {
"url": "https://gateway.pipeworx.io/bnr-ro/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/bnr-ro/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1875+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/bnr_exchange_rates \
-H 'Content-Type: application/json' \
-d '{}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/bnr_exchange_rates. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"bnr-ro": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-bnr-ro"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-bnr-ro
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Bnr Ro data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Bnr Ro?
National Bank of Romania (Banca Naţională a României, BNR) FX reference rates MCP. Keyless.
How do I install Bnr Ro?
It runs as a remote server. In Claude Code: claude mcp add --transport http bnr-ro 'https://gateway.pipeworx.io/bnr-ro/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Bnr Ro need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Bnr Ro open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Bnr Ro?
It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.