Canada Post MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CANADA_POST_API_KEY | No | Legacy Developer Program key. Authenticated fallback for Track, Rating, and Post Office APIs. | |
| CANADA_POST_MyMAIL_MOCK | No | Set true with CANADA_POST_MyMAIL_ENABLED for mock sample data. No login. | |
| CANADA_POST_API_PASSWORD | No | Legacy Developer Program password for the key above. | |
| CANADA_POST_DEVPORTAL_KEY | No | Developer Portal API Key for your app. Preferred route, used first. | |
| CANADA_POST_MyMAIL_ENABLED | No | Set true only on your own machine to enable MyMail. Default off. | false |
| CANADA_POST_CONTRACT_NUMBER | No | Your Canada Post contract number, if you have one. Needed for some rates. | |
| CANADA_POST_CUSTOMER_NUMBER | No | Your Canada Post customer number. Needed for commercial rates. | |
| CANADA_POST_DEVPORTAL_SECRET | No | Developer Portal API Secret for your app. Never commit this. | |
| CANADA_POST_MyMAIL_EXPORT_FILE | No | Path to a MyMail JSON file you saved yourself from the Canada Post app. |
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_parcelA | Track a Canada Post parcel by tracking number. Returns the live status from Canada Post public tracking, or an honest error when Canada Post blocks the request. Never invents a status. |
| get_ratesA | Get Canada Post shipping rates for a parcel route. Needs official Developer Program credentials in env for live rates; without them it reports honestly and links the public Find a Rate calculator. Never invents a rate. |
| find_post_officeA | Find Canada Post post offices near a place or postal code. Each result has a real address. Without API credentials it uses a recorded directory of real downtown Toronto offices, labelled as recorded data. |
| list_mymailA | List incoming mail from Canada Post MyMail. LOCAL ONLY and OPT-IN. Returns mock sample items only when CANADA_POST_MyMAIL_ENABLED=true and CANADA_POST_MyMAIL_MOCK=true, or items from a local export file you saved yourself. Fails cleanly when not configured. Never logs in. |
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 targets a clearly distinct resource and action: parcel tracking, rate quotes, post office lookup, and MyMail inbox listing. There is no plausible overlap that would cause an agent to misselect, and the descriptions reinforce the boundaries (live API vs. recorded data vs. local mock).
All four tools follow a snake_case verb_noun pattern (track_parcel, get_rates, find_post_office, list_mymail), which is predictable and readable. The only minor deviation is list_mymail, where the object is a brand name rather than a plural noun like list_mail_items.
Four tools is on the lean side but each maps to a real, non-redundant Canada Post capability, so nothing feels padded. It only falls short of 5 because the surface is thin enough that a user might reasonably expect adjacent operations (e.g. label creation or address validation) to be present.
The set covers the read-only lookups well (tracking, rates, offices, inbox), but there is no way to create a shipment or buy a label, no postal-code/address validation, and no delivery-standard/estimated-transit lookup. These are notable gaps for a server framed as Canada Post parcel services, even if the honest-fallback design suggests intentional read-only scope.