# boxberry-mcp

**Category:** 📦 Delivery  
**Repository:** https://github.com/theYahia/boxberry-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 105  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/boxberry-mcp

## Description
MCP server for Boxberry delivery API — city/point search, delivery calculation, tracking. 4 tools.

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

```json
"mcpServers": {
  "boxberry-mcp": {
    "command": "npx",
    "args": ["-y","@theyahia/boxberry-mcp"],
    "env": {
      "BOXBERRY_API_TOKEN": "",
      "PORT": ""
    }
  }
}
```

**Requires environment variables:** `BOXBERRY_API_TOKEN`, `PORT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What boxberry-mcp MCP server does

boxberry-mcp MCP server exposes Boxberry delivery operations to an MCP-compatible AI client. The package provides six tools covering common delivery workflows: finding cities, locating pickup points, calculating delivery cost and timing, tracking a shipment, checking whether a postal code belongs to a delivery zone, and listing services associated with a shipment.

The repository is archived, and ongoing development has moved to the `theYahia/WWmcp` monorepo. The current package remains available as `@theyahia/boxberry-mcp` on npm and is described as installable and usable in the same way as before. Issues and pull requests should be directed to the newer repository.

## How it works

An MCP client starts the package and communicates with its tools. In stdio mode, the client launches `npx -y @theyahia/boxberry-mcp` and passes the Boxberry API token through the process environment. For deployments that need a network endpoint, the package can start with the `--http` flag and exposes Streamable HTTP at `/mcp`; a health endpoint is available at `/health`.

The available operations are:

- `list_cities` searches the Boxberry city list by name.
- `list_points` returns pickup points for a specified city.
- `calc_delivery` calculates delivery price and estimated timing.
- `track` looks up a shipment using its tracking number.
- `zip_check` checks a postal code against the delivery zone.
- `list_services` lists services provided for a shipment.

Claude Code skills are also documented for tracking a shipment, calculating delivery by city and weight, and running a city-to-pickup-point-to-calculation workflow.

## Setup and configuration

The required setting is `BOXBERRY_API_TOKEN`, obtained from the Boxberry personal account. A stdio client can configure the npm package as an MCP command and provide this token in its environment.

HTTP mode starts with `BOXBERRY_API_TOKEN=<TOKEN> npx @theyahia/boxberry-mcp --http`. The default HTTP port is 3000, and `PORT` can override it, such as `PORT=8080`. A `smithery.yaml` file is included and also requires the Boxberry token.

## Tools and capabilities

The boxberry-mcp MCP server fits conversational delivery tasks where an agent needs structured access to Boxberry data rather than a user navigating the delivery account manually. It can combine several calls for a broader flow: identify a city, find pickup points there, and calculate delivery for a shipment. Separate tools support shipment tracking, postal-code validation, and service inspection.

## Limitations and notes

The source repository is no longer receiving updates. Its maintained location is the `servers/boxberry/` directory in `theYahia/WWmcp`; this repository points there for current development. Operation requires a valid Boxberry API token. The documented package supports stdio and Streamable HTTP transports, with HTTP health and MCP endpoints available when HTTP mode is selected.

_Full upstream README: https://allmcps.com/mcp/boxberry-mcp/readme_