kartverket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_addressA | Search Norwegian addresses by free text. Returns matching addresses with coordinates (EPSG:4258 / WGS84), postcode, postal area, municipality, and cadastre number (gårdsnummer/bruksnummer). Use when the user gives a street name or a full or partial address and needs the canonical record. |
| address_at_pointA | Reverse geocode: find the addresses closest to a latitude/longitude in Norway. Use when the user has coordinates and wants to know what is there. |
| search_placenameA | Search Norway's official place-name registry (Sentralt stedsnavnregister / SSR). Covers farms, islands, mountains, fjords, lakes, urban areas, and other named natural features — not street addresses. Use for named places that aren't street addresses. |
| elevation_at_pointA | Get ground elevation in metres at a coordinate in Norway, from the national 1m digital terrain model. Returns elevation above sea level and the terrain type (open ground, forest, water, etc.). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: forward and reverse geocoding for addresses, placename search, and elevation query. No overlap in functionality.
Tools follow a clear pattern: coordinate-based queries use '<resource>_at_point' and text-based searches use 'search_<resource>'. While not all verb_noun, the pattern is predictable and consistent.
With 4 tools, the set is well-scoped for a national geospatial server. Each tool covers a core function without unnecessary duplication.
Covers essential geospatial queries (address forward/reverse, placename search, elevation). Missing features like routing or structured geocoding, but core use cases are complete.