
Connects to Sveriges Riksbank's SWEA v1 API for querying Swedish central bank data. No API key required. Part of the Pipeworx gateway system, which means you can either use the dedicated Riksbank endpoint or access it through their unified gateway alongside 250+ other data sources. Supports the ask_pipeworx pattern where you ask questions in plain English instead of calling tools directly. Useful when you need Swedish economic indicators, interest rates, or monetary policy data in your AI workflows. Runs over streamable HTTP, so it works with any MCP client that supports remote transports.
Sveriges Riksbank (Sweden's central bank) SWEA v1 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 |
|---|---|
list_series | Browse/search the Riksbank SWEA catalogue of time series (interest rates and SEK exchange rates). Returns series IDs plus descriptions and available date ranges. Optionally filter by a case-insensitive substring matched against the series ID and descriptions, e.g. "policy", "rate", "EUR", or "exchange". Series IDs are string codes; well-known ones: SECBREPOEFF (policy rate, formerly repo rate), SECBDEPOEFF (deposit rate), SECBLENDEFF (lending rate), SEKEURPMI (EUR/SEK fixing), SEKUSDPMI (USD/SEK fixing), SEKGBPPMI (GBP/SEK), SEKJPYPMI (JPY/SEK). Omit query to list all (~117 series). |
get_observations | Time-series observations for one series over a date range. Pass a series ID and a from/to window (dates YYYY-MM-DD). Returns an array of {date, value}. Example: seriesId "SEKEURPMI" gives the daily EUR/SEK exchange-rate fixing; "SECBREPOEFF" gives the Riksbank policy rate. Use list_series to discover IDs. |
latest_observation | Most recent observation for a single series, as {date, value}. Example: seriesId "SECBREPOEFF" returns the current Riksbank policy rate; "SEKUSDPMI" returns the latest USD/SEK fixing. For the policy rate specifically, policy_rate also gives the previous rate and when it changed. |
policy_rate | The Riksbank's current policy rate (series SECBREPOEFF): the rate, the date it took effect, the previous rate and when that one took effect, plus recent decision history — computed from the daily series so a caller does not have to infer the decision date from latest_observation's bare {date, value}. |
cross_rates | Cross exchange rate between two SEK currency-fixing series over a date range. series1 is the base, series2 the quote; the result is series1/series2 per day. Example: series1 "SEKEURPMI", series2 "SEKUSDPMI" gives EUR/USD derived from the SEK fixings. Provide from (required) and optionally to (both YYYY-MM-DD); omit to to run through the latest date. Use SEK currency series IDs ending in "PMI" (see list_series). |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"riksbank-se": {
"url": "https://gateway.pipeworx.io/riksbank-se/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/riksbank-se/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/riksbank_se_list_series \
-H 'Content-Type: application/json' \
-d '{"query":"policy"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/riksbank_se_list_series. 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": {
"riksbank-se": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-riksbank-se"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-riksbank-se
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 Riksbank Se data" })
The gateway picks the right tool and fills the arguments automatically.
MIT