How to Connect BEX Express to Cursor via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → BEX Express, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

BEX Express + Cursor

BEX Express courier (Serbia) from an AI agent: shipment status history by shipment number, address labels as PDF, the BEX address directory of municipalities, places and streets, and parcel shops and depots. Creating and cancelling shipments is included, installed switched off.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

BEX_API_TOKEN

Step 1 — Get credentials

Setting up takes about 5 minutes once BEX has sent you the key. You need a contract with BEX Express, the Serbian courier, and an API key that BEX issues for that contract.

1. If you are not a BEX customer yet, ask for an offer at [email protected]: the API is only for contract customers.
2. Write to [email protected], ask for API access and name the contract it is for.
3. BEX replies with an API key and your KlijentId. Paste the key into BEX_API_TOKEN; it is sent as the X-AUTH-TOKEN header. Keep the KlijentId at hand: it identifies your company as the sender of a shipment.
4. Install the connector and run bex_express_list_municipalities. If it returns the list of municipalities, the key works.

What it reads: the status history of a shipment by its BEX shipment number (the one printed on the label), with every scan, status, date, place and the next expected event; the address labels of a shipment as a PDF; the BEX address directory of municipalities (opštine), places (mesta) with postcode, and streets; and about 120 parcel shops and depots with code, address, opening hours and coordinates.

Status codes: 1 registered, 11 picked up from the sender, 21 delivered, 25 to be returned to the sender, 30 returned to the sender, -21 address check by the call centre, -51 at customs. The AI tells you what they mean in plain words.

Labels: one A6 label per page, or four labels on an A4 sheet, for every parcel of a shipment or only one. The PDF is large, so the AI fetches it only when you want to print or save a label.

Addresses use BEX ids: BEX describes an address by municipality, place and street. The AI looks them up step by step, one municipality or one place at a time. The connector never asks BEX for every street of Serbia at once (almost 100,000 of them).

Two hosts and port 62503: tracking, labels and the address directory run on the normal HTTPS port, while the parcel shop list and creating and cancelling shipments run on https://api.bex.rs:62503. That port is reachable from AnythingMCP Cloud; on a self-hosted server behind a firewall that only allows port 443, those three tools fail.

Switched off at install: bex_express_create_shipments and bex_express_cancel_shipment. They announce real shipments for pickup by a courier or cancel them, so an administrator turns them on deliberately. Even then the AI first shows you the full shipment (sender, receiver, parcels, cash on delivery, insurance, who pays) or the shipment number to cancel, and waits for your yes. A shipment the courier has already picked up cannot be cancelled.

Common errors: 401 means the key is wrong or missing. 403 means the key works but that method is not enabled for your contract: ask [email protected]. Many BEX methods answer HTTP 200 with state false and a reason in err, so the AI reads those fields before reporting a result. The parcel shop list is the exception: there BEX sends state false with the text ok even when the list is complete.

The connector does not cover invoices or cash on delivery payouts, and it does not create or cancel shipments unless an administrator has turned those tools on.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Cursor

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Cursor reads MCP servers from ~/.cursor/mcp.json. Add this entry:

{
  "mcpServers": {
    "anythingmcp": {
      "url": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart Cursor.
3. Open Cursor → Settings → MCP and check that anythingmcp is listed and connected.
4. Start chatting: the agent can now call the BEX Express tools.

Available tools

Example prompts

• "Where is shipment 206897445 right now, and when is the next step expected?"
• "Which of these shipments went back to the sender: 206897445, 206897446 and 206897447?"
• "Which BEX parcel shops are there in Novi Sad, and are they open on Saturday?"
• "Get me the labels of shipment 206897445, four per A4 page, so I can print them."
• "Does BEX know Bulevar oslobođenja in Novi Sad? Give me the place and street ids for a shipment address."

FAQ

Does Cursor support custom MCP servers on the free tier? Yes, MCP is available on Hobby, Pro and Business plans.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT