Skip to main content
Glama
vinvuk

Apiverket MCP Server

by vinvuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOVDATA_API_KEYNoAPI key (sk_test_* for sandbox, sk_live_* for production)sk_test_demo
GOVDATA_API_URLNoApiverket API base URLhttp://localhost:3010

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
govdata_discoverA

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.

govdata_queryA

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

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_swedish_dataTemplate for analyzing Swedish government data — guides through discovery, querying, and analysis.

Resources

Contextual data attached and managed by the client

NameDescription
endpoint-catalogComplete list of all available Apiverket API endpoints with descriptions and parameters
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools serve clearly distinct purposes: govdata_discover for exploring available endpoints and govdata_query for retrieving data. No functional overlap exists.

Naming Consistency5/5

Both tools follow a consistent govdata_verb pattern using snake_case, making their purpose predictable.

Tool Count3/5

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.

Completeness4/5

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

ActivityInactive
ResponsivenessUnresponsive

Resources