A Swedish Monetary‑Policy Data MCP Server

Created By
aerugoa year ago
An MCP Server for Riksbank data (monetary policy, SWEA, SWESTR)
Overview

What is Swemo-MCP?

Swemo-MCP is an unofficial Monetary-Policy Data MCP Server that wraps Sveriges Riksbank’s open API into a Model-Context-Protocol (MCP) micro-service, providing a clean interface for accessing Swedish monetary policy data.

How to use Swemo-MCP?

To use Swemo-MCP, set up the project using Astral's uv for dependency management, and then invoke the provided tools through any MCP client or directly in Python scripts.

Key features of Swemo-MCP?

  • Provides a clean, async Python interface for accessing Riksbank data.
  • Exposes various economic series as MCP tools for easy access.
  • Supports both forecast values and realized data for historical analysis.

Use cases of Swemo-MCP?

  1. Analysts can retrieve and analyze historical monetary policy data.
  2. Journalists can access real-time economic forecasts for reporting.
  3. Researchers can utilize the data for economic modeling and analysis.

FAQ from Swemo-MCP?

  • Is Swemo-MCP an official Riksbank product?

No, it is an unofficial MCP server and may not always reflect the latest updates from the Riksbank.

  • How can I install Swemo-MCP?

You can install it by cloning the repository and using the command uv sync to set up the environment.

  • What programming language is used?

Swemo-MCP is developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aerugo
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

6 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago