Vepathos MCP server

Vepathos MCP

Large-scale delivery and fleet optimization for AI agents.

Vepathos solves vehicle routing problems (VRP) for last-mile fleets: it assigns stops to vehicles and sequences each route from one depot, at scales from dozens to thousands of stops.

This repository is the remote MCP adapter (mcp.vepathos.com). It is not a product of its own. Web, REST and MCP share the same Vepathos account, plan, features, limits and monthly stop quota.

<!-- BEGIN GENERATED: tools-table (vepathos-mcp tools --write-docs) -->

<!-- END GENERATED: tools-table -->

No tool switches an automation on: create_automation always writes it switched off, and only its owner turns it on in the dashboard, because a rule that is on spends their stops unattended.

There is no cancel tool. A submitted optimization runs to completion. Street addresses must go through geocodeaddresses (or, with imports on, importdeliveries) first; optimize_routes does not invent coordinates.

Status

Production runs 0.10.0 at https://mcp.vepathos.com/mcp and publishes all 15 tools: the import tools, the shareable map and manage_catalog are switched on there, so the "Available" column above describes what the code gates, not what this deployment withholds.

Vepathos is not listed in any directory yet, so a client has to add it as a custom connector with that URL. It is listed on Smithery.

Paid self-serve is off. A request the account's plan cannot run answers PLANUPGRADEREQUIRED with a contact_url, never a Stripe Checkout link, and the user retries without reconnecting once the account can run it.

Two ways to run it away from production:

geocodes for real. Everything in tests/ uses it.

• Local and CI: this server against a fake Core, a test double that neither routes nor

Import worker.

• Local against the real stack: the vepathos-api-doc MCP channel, the optimizer and the Smart

Connect (production target)

Add Vepathos → Connect → Sign in / Sign up → Authorize

Shortened. The full README is on GitHub.