Apiverket MCP Server
This server provides AI assistants with access to Swedish public government data through the Apiverket API, covering 139 endpoints across 16 categories.
Discover endpoints (
govdata_discover): Search and browse available API endpoints by keyword or category without making API calls — useful for finding the right endpoint before querying.Query government data (
govdata_query): Call any discovered endpoint withpath_paramsandquery_paramsto retrieve structured JSON data across domains like weather, transport, jobs, company info, and more.Inspect account & usage (
govdata_account): Check API key mode (sandbox/live), tier, daily usage, company-search/lookup quotas, and upgrade-relevant limits.Error handling & pagination: Receive structured recovery guidance on failures (e.g., 429 rate limit errors) and truncated large responses with pagination instructions.
Automated workflow guidance: Predefined discovery workflows support data families including transport, weather, geography, municipalities, jobs, government, culture, education, tourism, environment, and company data.
Data domains include:
🌦️ Weather & Climate: forecasts, warnings, air quality, observations
🚆 Transport: train departures, transit stops, transport statistics
🏛️ Government & Parliament: documents, members, committees, SFS/SOU legislation
👮 Police & Safety: events and stations by location
💼 Jobs: search, taxonomy, concepts, autocomplete
🏙️ Geography & Municipalities: population, KPIs, geometry, county/municipality codes
🏢 Company Data: search by name, look up by organisation number
⚡ Economy & Finance: exchange rates, electricity prices
🌱 Environment: EV charger locations, environmental data
🎓 Education, Culture, Tourism, and more
Apiverket MCP Server
An MCP (Model Context Protocol) server that gives AI assistants access to Swedish public data through the Apiverket API. It works with Claude Code, Claude Desktop, Cursor, VS Code, Gemini CLI-style MCP clients, and other MCP-compatible tools.
What it does
Tool | Purpose |
| Search and browse supported Apiverket endpoints before choosing a path |
| Call a discovered endpoint and return structured JSON or recovery guidance |
| Inspect sanitized key mode, tier, daily usage, company-search/company-lookup quota, and upgrade-relevant limits |
Agents should call govdata_discover before govdata_query instead of guessing /v1 paths. After a 429 or when a user asks about limits, agents should call govdata_account.
Related MCP server: SCB MCP Server
How Agents Should Use Apiverket
Discover: call
govdata_discoverwith the user's topic, not a guessed path.Check context: call
govdata_accountfor quota, tier, and production-readiness questions.Query: call
govdata_queryonly with a supported endpoint returned by discovery.Recover: if a request fails, use the structured recovery guidance before retrying.
Discovery includes family workflows for transport, weather, geography, municipalities, jobs, government, culture, education, tourism, environment, and company data. These workflows explain search/list/detail patterns, required codes, coordinates, date formats, pagination, and common recovery steps.
Quick Start
Claude Code / Claude Desktop
{
"mcpServers": {
"apiverket": {
"command": "npx",
"args": ["-y", "apiverket-mcp-server"],
"env": {
"GOVDATA_API_URL": "https://apiverket.se",
"GOVDATA_API_KEY": "sk_test_demo"
}
}
}
}Cursor / VS Code
{
"servers": {
"apiverket": {
"command": "npx",
"args": ["-y", "apiverket-mcp-server"],
"env": {
"GOVDATA_API_URL": "https://apiverket.se",
"GOVDATA_API_KEY": "sk_test_demo"
}
}
}
}Gemini CLI-Style MCP Config
{
"mcpServers": {
"apiverket": {
"command": "npx",
"args": ["-y", "apiverket-mcp-server"],
"env": {
"GOVDATA_API_URL": "https://apiverket.se",
"GOVDATA_API_KEY": "sk_test_demo"
}
}
}
}Keys And Limits
Variable | Default | Description |
|
| Apiverket API base URL |
|
| Sandbox key by default. Use a |
sk_test_demo is for setup and safe sandbox responses. It is useful for checking that your MCP client is wired correctly, but production workflows should use a live key. Free live keys are good for exploration; upgrade when daily API or company-search limits block a real workflow.
Company Data With Agents
Company search and company lookup have different jobs:
Use
govdata_discover(query: "company")to find the supported company endpoints.Use
/v1/companies/searchwhen the user only has a company name or uncertain organisation number.Cache the returned
org_number.Use
/v1/companies/{orgNumber}for repeated enrichment and automation.If company search returns 429, stop retrying until
reset_at; use lookup when org numbers are already known.
Company search and live company lookup have separate daily quota context by tier. govdata_account shows the configured key tier, remaining company-search quota, remaining company-lookup quota, reset time, and available upgrade tiers. Apiverket does not expose company board, officer, owner, or UBO subresource paths through the company API.
Common Family Workflows
Family | Good first query | Agent workflow |
Transport |
| Use station codes for |
Weather |
| Use city endpoints for simple weather, warnings for national alerts, and station/lat/lon flows for air quality or observations. |
Geography & municipalities |
| Find official municipality/county/place codes first; search KPIs before municipality KPI detail calls; request geometry only when needed. |
Jobs |
| Use |
Government & safety |
| Choose calendar, documents, members, committees, SFS, SOU, police events, or police stations based on the question. |
Culture, education & environment |
| Search first, then reuse returned IDs/codes for detail endpoints; ensure |
Tool Examples
# Discover endpoints
govdata_discover(query: "electricity prices")
govdata_discover(category: "Weather & Climate")
govdata_discover(query: "train departures")
govdata_discover(query: "municipality KPI")
govdata_discover(query: "jobs taxonomy")
# Query data after discovery
govdata_query(endpoint: "/v1/weather/{city}", path_params: {city: "stockholm"})
govdata_query(endpoint: "/v1/transport/trains/{station}", path_params: {station: "Cst"})
govdata_query(endpoint: "/v1/jobs/search", query_params: {q: "developer", limit: 5})
govdata_query(endpoint: "/v1/taxonomy/types")
govdata_query(endpoint: "/v1/companies/search", query_params: {q: "volvo", limit: 10})
govdata_query(endpoint: "/v1/companies/{orgNumber}", path_params: {orgNumber: "5560125790"})
# Inspect tier and quota state
govdata_account()Build From Source
git clone https://github.com/vinvuk/apiverket-mcp.git
cd apiverket-mcp
npm install
npm run buildHow It Works
The MCP server runs locally over stdio.
govdata_discoversearches the built-in endpoint catalog without an API call.govdata_querycalls Apiverket with the configured API key.Structured API errors are turned into recovery guidance for agents.
Large responses are truncated with pagination guidance.
Requirements
Node.js >= 18
An Apiverket API key, or
sk_test_demofor sandbox setup
License
MIT
Available Tools
2 toolsgovdata_discoverDiscover Apiverket EndpointsARead-onlyIdempotent
Search and browse available Swedish government data endpoints in the Apiverket API.
Use this tool to find the right endpoint before calling govdata_query. The API covers 139 endpoints across 16 categories including weather, transport, economy, health, environment, parliament, police, education, and more.
Args:
query (string, optional): Keyword to search across endpoint names, descriptions, and paths
category (string, optional): Filter by category name
When called with no arguments, returns all available categories with endpoint counts.
Examples:
Find weather endpoints: query="weather"
Browse transport category: category="Transport"
Find pension info: query="pension"
List all categories: (no arguments)
Returns: Matching endpoints with their paths, parameters, and descriptions.
Inputs: query, category.
govdata_queryQuery Apiverket APIARead-onlyIdempotent
Call any Apiverket API endpoint to retrieve Swedish government data.
Use govdata_discover first to find the right endpoint path and required parameters. Then call this tool with the endpoint path and any path/query parameters.
Args:
endpoint (string, required): The API path (e.g. "/v1/weather/{city}")
path_params (object, optional): Values for path parameters like {city}, {code}, {id}
query_params (object, optional): Query string parameters (q, limit, offset, lat, lon, etc.)
Examples:
Current weather in Stockholm: endpoint="/v1/weather/{city}", path_params={"city": "stockholm"}
Search jobs: endpoint="/v1/jobs/search", query_params={"q": "developer", "limit": 5}
Train departures from Stockholm Central: endpoint="/v1/transport/trains/{station}", path_params={"station": "Cst"}
Exchange rates: endpoint="/v1/rates"
Population by municipality: endpoint="/v1/population/{municipalityCode}", path_params={"municipalityCode": "0180"}
Police events in Stockholm: endpoint="/v1/police/events", query_params={"location": "Stockholm", "limit": 10}
Find EV chargers near a location: endpoint="/v1/infrastructure/ev-chargers", query_params={"lat": 59.33, "lon": 18.07}
Returns: The API response as JSON, containing a "meta" envelope with request info and a "data" object with the actual data.
Error handling:
Returns clear error messages if the API is unreachable, the endpoint doesn't exist, or parameters are invalid
Large responses are automatically truncated with pagination guidance
Inputs: endpoint (required), path_params, query_params.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools serve clearly distinct purposes: govdata_discover for exploring available endpoints and govdata_query for retrieving data. No functional overlap exists.
Both tools follow a consistent govdata_verb pattern using snake_case, making their purpose predictable.
With only 2 tools for a domain covering 139 endpoints across 16 categories, the count is minimal but appropriate for the discover-query pattern. However, it may feel thin for the broad scope.
The pair covers the complete lifecycle: discovery then retrieval. For a read-only government data API, this is sufficient. Minor gaps like built-in pagination handling are mitigated by error messages.
Maintenance
Related MCP Connectors
Swedish company data (Bolagsverket, SCB) for AI agents, verified, with history and annual reports
Swedish company data for AI agents: search, board, history, financials. Sandbox: fictional firms.
Swedish public data as read-only tools: registries, statistics, domains, transport, energy.
Swedish B2B intelligence for AI agents: insolvency risk, procurement, BRF health and more.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides access to Sweden's comprehensive municipal and regional statistics database with semantic search capabilities. Enables natural language queries against thousands of Key Performance Indicators covering various aspects of Swedish public sector data.16Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to search, access, and retrieve official Swedish statistics from Statistics Sweden (SCB), providing access to 1,200+ tables covering demographics, economy, environment, labor market, and education with 75+ years of historical data.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables easy access to open data from the Swedish National Agency for Education, allowing querying and integration of educational statistics and facts through large language models.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query Swedish Parliament open data through natural language.95 npmMIT