postnord-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTNORD_LOCALE | No | Language for human-readable strings: en, sv, no, da, fi | en |
| POSTNORD_API_KEY | Yes | Your API key from the developer portal | |
| POSTNORD_SANDBOX | No | Set to true to use the sandbox environment (atapi2.postnord.com) | false |
| POSTNORD_BASE_URL | No | Override the API base URL entirely | https://api2.postnord.com |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| track_shipmentA | Track a PostNord shipment by shipment ID, item ID (parcel number), or customer reference. Returns the full tracking history with status events, estimated delivery time, and delivery details. |
| find_service_pointsA | Find the nearest PostNord service points (pickup/drop-off locations) by address or postal code. Returns names, addresses, opening hours, and coordinates. |
| find_service_points_by_coordinatesA | Find the nearest PostNord service points (pickup/drop-off locations) by geographic coordinates (WGS84 latitude/longitude). |
| get_transit_timeA | Estimate PostNord transit time between two postal codes for a given service code. Service codes depend on your PostNord agreement (e.g. 19 for MyPack Collect). |
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
track_shipment and get_transit_time are clearly distinct, but find_service_points and find_service_points_by_coordinates perform the same lookup with different input types. The suffix and explicit descriptions prevent serious confusion.
All tool names follow a lowercase verb_noun pattern with consistent snake_case. find_service_points_by_coordinates is longer but still fits the same convention.
Four tools is well within the ideal range and each covers a meaningful PostNord workflow: tracking, service point lookup, and transit time estimation. There is no obvious redundancy.
The set covers the core read-only PostNord use cases well, especially tracking and pickup locations. It lacks a way to enumerate valid service codes or create shipments, but those are minor gaps for typical tracking and collection queries.