Parcel MCP Server
This MCP server lets you inspect Parcel delivery tracking and carrier data, and optionally add deliveries when writes are enabled.
Check Parcel credential discovery and whether write tools are available, without making an API call.
List all active or recent deliveries, including status, expected dates, and cached carrier events.
Retrieve one delivery by exact tracking number from the active or recent views.
List the complete Parcel carrier catalog of codes and names.
Search carriers by code or display name.
Add a delivery with tracking number, carrier code, description, language, push confirmation, postcode, and email, only when
PARCEL_ALLOW_WRITES=1.Use Parcel’s cached read data; reads do not trigger a carrier refresh.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Parcel MCP Server Track package 1Z999AA10123456784"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Parcel MCP Server
An MCP server for Parcel delivery tracking. It covers every field and operation in Parcel's documented external API, provides the daily carrier catalog, and runs through local stdio or a hosted Cloudflare remote connector.
This project is not affiliated with Ivan Pavlov or Parcel.
Coverage
Parcel API | MCP tools |
|
|
|
|
|
|
Parcel does not document edit, delete, archive, or forced-refresh endpoints. This server does not claim those capabilities.
Related MCP server: Parcel MCP Server
Tools
parcel_auth_statusreports credential discovery and the write gate without an API call.parcel_list_deliveriesreturns every delivery and event from theactiveorrecentAPI view.parcel_get_deliveryselects one exact tracking number from those API views.parcel_list_carriersreturns the complete carrier code map.parcel_find_carrierssearches carrier names and codes.parcel_add_deliverysubmits one delivery and supportstracking_number,carrier_code,description,language,send_push_confirmation,postcode, andemail.
The add tool is not advertised unless PARCEL_ALLOW_WRITES=1. This prevents an MCP client from invoking a write when the server was intended to be read-only.
Parcel API limits
Parcel Premium is required.
Delivery reads return cached data and do not trigger a carrier refresh.
Reads are limited to 20 requests per hour.
Adds are limited to 20 requests per day, including failed requests.
The add endpoint accepts one delivery per request.
Newly added deliveries can show no data until Parcel's next server update.
Local installation
Use Node.js 20 or newer. Generate an API key at Parcel Web Access, then use one of these credential methods:
export PARCEL_API_KEY="your-parcel-api-key"
export PARCEL_ALLOW_WRITES=1
npx -y @oliverames/mcp-server-for-parcel@latestThe server also supports:
PARCEL_API_KEY_FILE, a small file containing only the key.PARCEL_OP_PATH, anop://reference read through the 1Password CLI.Codex
~/.codex/config.tomland Claude~/.claude/settings.jsonenvironment sections.
Credential priority is the process environment, host configuration, key file, then 1Password. The server never sends the key outside https://api.parcel.app and refuses redirects.
Claude Desktop, Claude Code, Codex, Hermes, and Antigravity
The repository includes native manifests for each host. The generic configuration is:
{
"mcpServers": {
"parcel-mcp-server": {
"command": "npx",
"args": ["-y", "@oliverames/mcp-server-for-parcel@latest"],
"env": {
"PARCEL_API_KEY": "${PARCEL_API_KEY}",
"PARCEL_OP_PATH": "${PARCEL_OP_PATH}",
"PARCEL_ALLOW_WRITES": "1"
}
}
}
}Leave PARCEL_ALLOW_WRITES empty for a read-only server.
Error reporting
Error reporting is off by default. If you set SENTRY_DSN, the local server sends unexpected tool failures, Parcel 5xx responses, and fatal errors to that Sentry project; without it, @sentry/node is never loaded. Reporting needs Node 20.19 or newer and is skipped quietly on older runtimes.
Each report carries only the error type, a fixed message, stack frames with package-relative paths, the tool name, and the HTTP status of a failed Parcel response. Tracking numbers, package descriptions, carrier events, locations, postcodes, email addresses, tool arguments, error messages, Parcel responses, breadcrumbs, user data, and request data are removed before anything is sent. A missing API key, an unknown tracking number, and Parcel's own 4xx or validation answers are not reported. The hosted connector does not use this setting.
Hosted Cloudflare connector
The worker/ directory provides an OAuth 2.1 protected Streamable HTTP endpoint at https://parcel.amesvt.com/mcp, plus legacy SSE for older clients. During authorization, the connector asks for a Parcel API key, validates it against Parcel, encrypts it with AES-GCM, and stores it per connection. The key never enters the connector's OAuth token or MCP Durable Object state.
The connector supports PKCE S256, dynamic client registration, optional write access, origin filtering, separate consent-signing and data-encryption keys, encrypted key deletion, and security headers. See the deployment guide.
The production deployment at parcel.amesvt.com is private. Cloudflare stores an allowlist containing only the SHA-256 hash of Oliver Ames' Parcel API key, so authorization attempts using any other Parcel key are rejected.
Development and verification
npm install
npm test
npm run smoke:list-tools
npm run smoke:live-tool
npm run smoke:packed
npm run release:check
npm pack --dry-runThe packed-install test installs the actual tarball and launches both declared bin names through npm's relative symlinks. CI tests Node 20 and 22, audits dependencies, scans secrets, and tests the Worker.
Security and privacy
See SECURITY.md, the hosted connector privacy notice, and Error reporting for the optional local Sentry setting. Do not commit Parcel API keys. If one is exposed, revoke it through Parcel Web Access and generate a replacement.
License
MIT. Copyright 2026 Oliver Ames.
Available Tools
5 toolsparcel_auth_statusParcel Authentication StatusARead-onlyIdempotent
Inspect Parcel credential discovery and write-tool availability without calling Parcel.
Inputs: no named parameters.
parcel_find_carriersFind Parcel CarriersARead-onlyIdempotent
Search the complete Parcel carrier catalog by code or display name before adding a delivery.
Inputs: query (required), limit, response_format.
parcel_get_deliveryGet Parcel DeliveryARead-onlyIdempotent
Find one delivery by exact tracking number within Parcel's active or recent API response and return all of its cached events.
Inputs: tracking_number (required), filter_mode, response_format.
parcel_list_carriersList Parcel CarriersARead-onlyIdempotent
Return the complete, daily-updated map of Parcel carrier codes to names. This covers GET /external/supported_carriers.json and requires no API key.
Inputs: response_format.
parcel_list_deliveriesList Parcel DeliveriesARead-onlyIdempotent
Return Parcel's complete recent or active delivery list, including status, expected dates, and every cached carrier event. This covers GET /external/deliveries/.
Inputs: filter_mode, response_format.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Track parcels across 2,500+ carriers and 3PLs: live delivery status, event history, carrier lookup.
Track parcels + ocean containers across 549 total carriers via REST and four existing MCP tools.
Configure parcelLab journeys, tracking pages and returns portals, and query delivery analytics.
Real-time order tracking for Shopify merchants: look up, list, and refresh shipments.
Related MCP Servers
- AlicenseBqualityDmaintenanceAllows tracking of parcel deliveries across various carriers using the 17track.net API, with automatic or manual carrier detection.223 npm6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to track and manage deliveries by interacting with the Parcel delivery tracking API. Users can add new shipments, retrieve active delivery statuses, and look up carrier information through natural language.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables users to manage package deliveries through the Parcel.app tracking API. It allows AI clients to list active or recent deliveries and add new packages directly to a Parcel account using tracking numbers and carrier codes.23 npm1GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables package tracking across multiple carriers by auto-detecting the carrier from a tracking number and returning structured events. Supports USPS, UPS, FedEx, DHL, India Post, Delhivery, BlueDart, and Aramex.MIT