
Connects Claude to the South African Reserve Bank's public data APIs without requiring authentication. Part of the Pipeworx gateway, which routes requests to 250+ data sources through a single endpoint. You can query SARB data directly through exposed tools or use the ask_pipeworx natural language interface to have the gateway select and invoke the right API calls automatically. Useful when you need South African monetary policy data, exchange rates, or central bank statistics in your AI workflows. The streamable HTTP transport means it works with any MCP client that supports remote servers. The source repo doesn't list specific tools, but it's MIT licensed and runs hosted, so there's nothing to deploy.
South African Reserve Bank (SARB) Web API MCP. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1819+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
| Tool | Description |
|---|---|
sarb_policy_rate | The SARB (South African Reserve Bank) Policy Rate — South Africa's benchmark monetary-policy interest rate, set by the Monetary Policy Committee. Returns the current rate, the date it took effect, the previous rate and when that one took effect, plus recent decision history (TimeseriesCode MMRD002A), computed from several years of daily observations rather than sarb_timeseries's narrow default window. |
sarb_home_rates | Current headline South African rates shown on the SARB home page: CPI & PPI inflation, SARB Policy Rate, prime lending rate, government bond yields, Sabor/Zaronia money-market rates, and key Rand exchange rates (USD/GBP/EUR). Each item includes its TimeseriesCode for use with the sarb_timeseries tool. No arguments. |
sarb_current_market_rates | Current South African money-market rates: SARB Policy Rate, Sabor, Zaronia. Each item includes a TimeseriesCode usable with the sarb_timeseries tool. No arguments. |
sarb_cpd_rates | Current Corporation for Public Deposits (CPD) interest rates: interest charged and interest earned. Each item includes a TimeseriesCode usable with the sarb_timeseries tool. No arguments. |
sarb_exchange_rates | Selected South African Rand exchange rates. frequency="daily" (default) returns latest daily rates (Rand per USD, GBP, Euro, etc.). frequency="monthly" returns latest monthly figures including the nominal and real effective exchange rate indices. Each item includes a TimeseriesCode usable with the sarb_timeseries tool. |
sarb_timeseries | Historical observation series for a single SARB indicator, identified by its TimeseriesCode (obtain codes from home_rates, current_market_rates, cpd_rates or exchange_rates). Examples: "MMRD002A" (SARB Policy Rate — or use sarb_policy_rate directly), "MMRD000A" (prime lending rate), "EXCX135D" (Rand per US Dollar), "CPI1000F" (CPI). Optionally bound the range with start_date and end_date (YYYY-MM-DD); omit both for the most recent ~25 points, not the full history. An unknown code and a valid code with no data in range both come back as a named no_data error (the SARB itself cannot tell them apart). |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"sarb-za": {
"url": "https://gateway.pipeworx.io/sarb-za/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/sarb-za/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 1819+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/sarb_policy_rate \
-H 'Content-Type: application/json' \
-d '{}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/sarb_policy_rate. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"sarb-za": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-sarb-za"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-sarb-za
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.
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 Sarb Za data" })
The gateway picks the right tool and fills the arguments automatically.
MIT