PostEx MCP Server

What is PostEx MCP Server?

An MCP server that provides tools for interacting with various endpoints of the PostEx Merchant API (v4.1.9). It is intended for developers who need to manage PostEx orders, addresses, tracking, and related operations through a standardized protocol.

How to use PostEx MCP Server?

Install dependencies (@modelcontextprotocol/sdk, zod, node-fetch@2), then run the server with Node.js, passing your PostEx API token as a command-line argument: node index.js <YOUR_POSTEX_API_TOKEN>. The server connects via standard I/O and listens for MCP requests.

Key features of PostEx MCP Server

• Exposes 14 tools covering order, address, and tracking operations.
• Validates input parameters using Zod schemas.
• Securely passes API token via command line.
• Graceful shutdown on SIGINT and SIGTERM signals.
• Uses node-fetch for HTTP requests to PostEx API.

Use cases of PostEx MCP Server

• Automate order creation and booking from an AI assistant.
• Retrieve operational cities and merchant addresses for logistics workflows.
• Track single or multiple orders programmatically.
• Manage shipper advice (retry/return) for failed deliveries.
• Cancel orders and check payment settlement status.

FAQ from PostEx MCP Server

What runtime and dependencies are required?

Node.js (LTS recommended) and npm/yarn. Dependencies include @modelcontextprotocol/sdk, zod, and node-fetch@2.

How do I obtain an API token?

A valid PostEx Merchant API Token must be obtained from your PostEx merchant account or representative.

Which PostEx API endpoints are not implemented?

Endpoints that return PDF files (generate-load-sheet, get-invoice) are not implemented in this version.

How does authentication work?

The API token is passed as a command-line argument and used in the Authorization header for all API calls.

How is the server connected to MCP?

The server uses standard I/O for communication and logs status messages to standard error.