inpost-consumer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INPOST_SHIPX_BASE_URL | No | Override ShipX tracking base URL | ShipX default |
| INPOST_CONSUMER_CONFIG | No | Path to the local auth/config JSON | OS app-config dir inpost-consumer-mcp/config.json |
| INPOST_CONSUMER_BASE_URL | No | Override mobile API base URL | mobile API default |
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 |
|---|---|
| inpost_consumer_login_send_smsA | Send a one-time login code by SMS to your phone. Next: inpost_consumer_login_confirm with the code from the message. |
| inpost_consumer_login_confirmA | Enter the SMS code to sign in. Saves your session on this device so you can list parcels and open lockers. |
| inpost_consumer_logoutA | Sign out and remove saved login(s) from this device. Does not change anything in the InPost app. |
| inpost_consumer_login_sessionsA | List phone numbers currently signed in on this device, with when each session expires. Login codes refresh automatically when you use other tools. |
| inpost_consumer_list_parcelsA | List your InPost parcels (status, locker, pickup code when available). Statuses are kept up to date with public tracking. Optional filter by status (e.g. ready_to_pickup, delivered) — case does not matter. |
| inpost_consumer_get_parcelA | Get details for one parcel by shipment number (or a unique short prefix): status, locker, pickup code, and QR payload for the app/scanner. |
| inpost_consumer_locker_openA | Remotely open the Paczkomat compartment for a parcel. Anyone standing at the machine can take it — only use when you are there. Set confirm=true to proceed. Prefer picking up in person at the correct locker. |
| inpost_consumer_locker_finishA | End a Paczkomat pickup session after opening (or if you need to tear it down). Use the session id returned by inpost_consumer_locker_open. |
| inpost_consumer_trackA | Public tracking for any InPost shipment number (no login required for full numbers). If you pass a short prefix, it is matched against your signed-in parcels when needed. |
| inpost_consumer_list_returnsA | List your InPost return tickets. Optionally filter by status. |
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 10 tools
Each tool has a clearly distinct purpose: login flow tools are separate from parcel listing/detail, locker operations are distinct from tracking and returns. No two tools overlap in a way that would cause misselection; even list_parcels and get_parcel are clearly list vs. single-item operations.
All tools share the 'inpost_consumer_' prefix, and most follow a verb_noun pattern (list_parcels, get_parcel, track, list_returns). However, some names are structured as noun_verb (locker_open, locker_finish) or use a domain prefix (login_send_sms, login_sessions, login_confirm), creating minor inconsistency in the verb/noun order.
Ten tools is well within the ideal 3-15 range for a consumer-focused InPost service. Each tool covers a necessary part of the user journey—auth, parcel viewing, locker operation, tracking, and returns—without unnecessary bloat or sparseness.
The tool surface covers the core lifecycle: login, logout, session management, listing and getting parcels, opening and finishing locker sessions, tracking, and listing returns. Minor gaps exist, such as no per-return detail view or explicit support for creating a return, but these are edge cases and the essential workflows are fully supported.