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.

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 geocode_addresses (or, with imports on, import_deliveries) first; optimize_routes does not invent coordinates.

Status

Production runs 0.11.1 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.

manage_catalog saves three kinds of thing: a vehicle, a depot, and a fleet grouping vehicles the account already has. A fleet's units is what it holds standing, never how many go out on one run, which is vehicles[].count on optimize_routes. To run with a saved fleet, read it with list_fleet and pass its vehicles: optimize_routes takes no fleet_id.

Vepathos is listed in the official MCP registry as com.vepathos/vepathos, on Smithery, and on Glama. Directories take a snapshot when they crawl, so a listing can lag a deployment by a day; the registry entry is republished on every version bump.

Paid self-serve is off. A request the account's plan cannot run answers PLAN_UPGRADE_REQUIRED 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:

• Local and CI: this server against a fake Core, a test double that neither routes nor geocodes for real. Everything in tests/ uses it.

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

Related MCP server: Syncnox MCP Server

Connect (production target)

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

1. Discover Vepathos from Claude or another MCP client.

2. Connect. The client signs in (or creates a Free / Duck account) at api.vepathos.com.

3. Authorize the client to optimize routes with that account.

4. Call optimize_routes. If the plan cannot run the request, the tool returns PLAN_UPGRADE_REQUIRED with upgrade_url (when paid plans are on) or contact_url (Free-only, until Stripe is configured). Payment, when enabled, is handled entirely by Stripe. Retry without reconnecting after the account can run the job.

No API keys and no JSON config for that flow. See docs/onboarding.md.

Developers and headless agents

Create a Vepathos dashboard credential with scope mcp:optimize and send

Authorization: Bearer <client_id>:<client_secret>

to https://mcp.vepathos.com/mcp. Usage counts against the same account plan as the web app and the REST API.

Example (3,200 deliveries)

{
  "depot": { "latitude": 40.7128, "longitude": -74.0060 },
  "vehicles": [
    { "vehicle_id": "van", "count": 35, "max_weight_kg": 900, "max_volume_m3": 8.0 }
  ],
  "stops": [
    {
      "stop_id": "ORD-10045",
      "latitude": 40.7306,
      "longitude": -73.9352,
      "weight_kg": 18.5,
      "volume_m3": 0.04,
      "time_window": { "start": "09:00", "end": "12:00" }
    }
  ],
  "schedule": {
    "date": "2026-10-01",
    "route_start_time": "07:30",
    "time_zone": "America/New_York",
    "service_time_minutes": 4
  }
}

Every stop needs latitude and longitude. Addresses are not geocoded. Weight, volume and time windows are optional; if you set a capacity on any vehicle, every vehicle and every stop must include that field. Time windows require schedule.route_start_time.

Results stay available for 24 hours. detail=summary is compact (totals and a page of routes). detail=stops returns ordered stop_id + arrival time, without echoing coordinates.

Full schemas and errors: docs/tools.md.

Run locally

Requires Python 3.12+.

python3.12 -m venv .venv && .venv/bin/pip install -e ".[dev]"
cp .env.example .env
docker compose up --build

The MCP endpoint is http://127.0.0.1:8080/mcp with Authorization: Bearer dev-bearer-token-change-me. That compose stack talks to the fake Core, not the optimizer.

.venv/bin/pytest -m "not integration"
.venv/bin/mypy
.venv/bin/ruff check src tests devtools

MCP Inspector and the integration against the real local stack: docs/testing.md.

Privacy

The tools accept coordinates, optional weight/volume/time windows and your own stop and vehicle ids. Street addresses reach Smart Import through geocode_addresses and import_deliveries and are not echoed back. Results do not repeat coordinates, logs omit tokens, payloads and coordinates, and hosted results are kept for 24 hours.

Account and logistics data follow the public policy at vepathos.com/privacy, which carries an MCP section. See also docs/security.md and SECURITY.md.

Research & benchmarks

The Vepathos last-mile optimizer is described in a public technical report: doi:10.5281/zenodo.19859531. That deposit is not a peer-reviewed publication.

Docs

License

Apache License 2.0