# Easypost [Health: Active]

**Category:** 📦 Delivery  
**Repository:** https://github.com/pipeworx-io/mcp-easypost  
**GitHub Stars:** 0  
**npm Downloads (last month):** 408  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/easypost

## Description
EasyPost MCP — multi-carrier shipping rates + package tracking (easypost.com)

## Tools
Capabilities this server exposes over MCP:

- **easypost_rates** — Get shipping rate quotes from `<from_zip>` to `<to_zip>` for a parcel — returns multi-carrier rates (USPS, UPS, FedEx, etc.) with price, service level, and estimated delivery days. Example: easypost_rates({ from_zip: "94105", to_zip: "10001", weight_oz: 16, _apiKey: "your-key" })
- **easypost_track** — Track a package by tracking number — returns current status, carrier, estimated delivery date, and recent scan events. Example: easypost_track({ tracking_code: "9400100000000000000000", carrier: "USPS", _apiKey: "your-key" })

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "easypost": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-easypost"]
  }
}
```

## Documentation

## What Easypost does

Easypost provides two shipping-focused MCP tools through Pipeworx. `easypost_rates` accepts origin and destination ZIP codes plus parcel weight, then returns rate options from carriers such as USPS, UPS, and FedEx. Results include the quoted price, service level, and expected delivery time.

`easypost_track` looks up a shipment using its tracking code and, optionally, the carrier. Its response includes the latest shipment status, carrier information, estimated delivery date, and recent scan events. Tool calls can receive an EasyPost API key through the `_apiKey` argument.

The integration is independent and unofficial, and is not published or endorsed by EasyPost.

## How it works

The hosted connection uses the Pipeworx MCP endpoint at `https://gateway.pipeworx.io/easypost/mcp`. Add that URL to an MCP client to expose the Easypost tools remotely. The endpoint also lists shared Pipeworx meta-tools, including `ask_pipeworx`, `discover_tools`, `search_within`, and memory-related tools. These shared tools can route questions beyond the Easypost pack, so the complete tool list is larger than the two shipping tools described here.

A full Pipeworx connection at `https://gateway.pipeworx.io/mcp` exposes the broader catalog directly. Both connection styles use the same gateway; the pack URL determines which tools are listed directly.

The local npm package, `@pipeworx/mcp-easypost`, acts as a stdio relay. An MCP client starts it with `npx`, and the relay forwards requests to the hosted gateway. It therefore requires network access and cannot operate offline.

## Setup and configuration

For a hosted setup, add the following server entry to an MCP client configuration:

```json
{
  "mcpServers": {
    "easypost": {
      "url": "https://gateway.pipeworx.io/easypost/mcp"
    }
  }
}
```

For the local bridge, use:

```json
{
  "mcpServers": {
    "easypost": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-easypost"]
    }
  }
}
```

The npm bridge can authenticate to Pipeworx with `PIPEWORX_API_KEY`. Anonymous use is limited to 50 calls per day, while a free Pipeworx account raises the allowance to 200 calls per day. Set `PIPEWORX_META_TOOLS=1` if the local bridge should also list the shared gateway tools.

Tool requests may pass the EasyPost credential as `_apiKey`. The gateway does not provide an EasyPost key on the caller’s behalf. The HTTP and npm options use the same remote gateway, and calls are metered in the same way.

## Tools and capabilities

- `easypost_rates`: compare carrier quotes for a route and parcel weight.
- `easypost_track`: retrieve shipment status and recent tracking events.
- `ask_pipeworx`: ask a natural-language question that the gateway routes to an appropriate tool.
- Hosted MCP access over HTTPS.
- Local stdio access through the npm package.

## Limitations and notes

The server depends on network access to Pipeworx. The local bridge has no offline mode. Pack endpoints always include Pipeworx’s shared meta-tools, and there is no option to remove them from a pack connection; use the full gateway when connecting to multiple packs is preferable.

The integration is unofficial. When using a proxy with the local bridge, Node’s built-in `fetch` does not automatically use `HTTPS_PROXY`; newer Node versions can be configured with `NODE_USE_ENV_PROXY=1`.

For clients without an MCP connection, Pipeworx provides HTTP tool inspection and invocation endpoints. Calling the shipping tools still requires the relevant API key.

_Full upstream README: https://allmcps.com/mcp/easypost/readme_