Parcel MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PARCEL_API_KEY | No | Your Parcel API key. Generate at Parcel Web Access. | |
| PARCEL_OP_PATH | No | A 1Password op:// reference to your Parcel API key. | |
| PARCEL_ALLOW_WRITES | No | Set to '1' to enable write operations (parcel_add_delivery). Leave empty or unset for read-only mode. | |
| PARCEL_API_KEY_FILE | No | Path to a file containing only the Parcel API key. |
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 |
|---|---|
| parcel_auth_statusA | Inspect Parcel credential discovery and write-tool availability without calling Parcel. |
| parcel_list_deliveriesA | Return Parcel's complete recent or active delivery list, including status, expected dates, and every cached carrier event. This covers GET /external/deliveries/. |
| parcel_get_deliveryA | Find one delivery by exact tracking number within Parcel's active or recent API response and return all of its cached events. |
| parcel_list_carriersA | Return the complete, daily-updated map of Parcel carrier codes to names. This covers GET /external/supported_carriers.json and requires no API key. |
| parcel_find_carriersA | Search the complete Parcel carrier catalog by code or display name before adding a delivery. |
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 5 tools
Each tool addresses a distinct concern: authentication status, listing deliveries, fetching a single delivery, listing carriers, and searching carriers. There is no overlap in purpose or output type.
All tools share the parcel_ prefix and use snake_case. Most follow a verb_noun structure (list_deliveries, get_delivery, list_carriers, find_carriers), but parcel_auth_status is a noun phrase rather than verb_noun, creating a minor deviation from the otherwise consistent pattern.
With 5 tools, the server is well-scoped for its domain of Parcel delivery and carrier lookups. Each tool serves a clear purpose, and the count is within the recommended range for a focused integration.
The read-side surface is well covered (list/get deliveries, list/search carriers), but the mention of 'adding a delivery' in find_carriers implies a write operation that is missing. There is no add_delivery or remove_delivery tool, leaving an incomplete lifecycle.