ESGO MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ESGO MCP Server Find free capacity from 47057 Duisburg to 80331 München for 12 t next week."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ESGO MCP server
Lets AI assistants (Claude, Cursor, VS Code, Windsurf and others that speak the Model Context Protocol) use the ESGO API: search for matching empty-run capacity in road freight and publish open transport requests, in plain language.
"Find free capacity from 47057 Duisburg to 80331 München for 12 t next week."
Alpha. The tools follow the ESGO API v1 automatically (see below).
How it works
Every operation of the ESGO API becomes one tool, built at start-up from the live OpenAPI spec at api.es-go.de/v1/openapi.json. When ESGO adds an endpoint, it is available as a tool the next time the server starts, without updating this package. If the API cannot be reached at start-up, the server uses the copy of the spec it ships with.
Tools that only read (me_retrieve, matches_search, open_requests_list_matches)
are marked read-only; tools that create data (open_requests_create) are not, so
your assistant asks before calling them.
Related MCP server: logistics-mcp
Access
You need an ESGO API key; there is no self-service sign-up yet. Request access at es-go.de/developers. The key stays on your machine and is only sent to the ESGO API.
Installation
The server runs locally and is started by your AI app. You need
uv; uvx downloads and runs the package on demand.
Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json),
Windsurf and others with the same format:
{
"mcpServers": {
"esgo": {
"command": "uvx",
"args": ["esgo-mcp"],
"env": { "ESGO_API_KEY": "esgo_live_..." }
}
}
}Claude Code:
claude mcp add esgo -e ESGO_API_KEY=esgo_live_... -- uvx esgo-mcpVS Code (.vscode/mcp.json):
{
"servers": {
"esgo": {
"command": "uvx",
"args": ["esgo-mcp"],
"env": { "ESGO_API_KEY": "esgo_live_..." }
}
}
}Without uv: pip install esgo-mcp, then use esgo-mcp as the command.
Variable | Meaning |
| your ESGO API key (required for calls) |
| optional, default |
Tools (as of October 2026)
The list comes from the API itself, so it may already be longer when you read this.
Tool | Endpoint | Changes data |
|
| no |
|
| no |
|
| yes |
|
| no |
Errors of the API (for example [429] daily_quota_exceeded or
[422] invalid_parameter (param: weight_kg)) are returned to the assistant as
tool errors, so it can correct the input or tell you.
Related
Python SDK: pypi.org/project/esgo
.NET SDK: nuget.org/packages/Esgo
API reference: api.es-go.de/v1/docs
Changelog: CHANGELOG.md
License
MIT, see LICENSE.
ESGO MCP server (Deutsch)
Damit können KI-Assistenten (Claude, Cursor, VS Code, Windsurf und andere, die das Model Context Protocol sprechen) die ESGO API nutzen: passende Leerfahrten im Straßengüterverkehr suchen und offene Transportanfragen einstellen, in normaler Sprache.
So funktioniert es: Jeder Endpunkt der ESGO API wird zu einem Werkzeug. Der Server baut die Werkzeuge beim Start aus der aktuellen OpenAPI-Spezifikation. Neue Endpunkte sind damit beim nächsten Start da, ohne Update dieses Pakets. Ist die API beim Start nicht erreichbar, nimmt der Server die mitgelieferte Kopie. Werkzeuge, die Daten anlegen, sind entsprechend markiert; der Assistent fragt vorher nach.
Zugang: Du brauchst einen API-Schlüssel von ESGO, anzufragen unter es-go.de/developers. Der Schlüssel bleibt auf deinem Rechner und geht nur an die ESGO API.
Einrichtung: siehe die Konfigurationsbeispiele oben. Benötigt wird
uv; uvx esgo-mcp lädt und startet das Paket.
Lizenz: MIT, siehe LICENSE.
Available Tools
4 toolsmatches_searchSearch matching capacityARead-onlyIdempotent
Search matching capacity
Finds trips whose route, time and free capacity fit your shipment. Prices are non-binding estimates; a fixed price is the standing offer of the carrier. Counts against the daily quota "matches_search".
Required API key scope: matches:read.
Inputs: origin (required), weight_kg (required), destination (required), service_ids, +2 more.
me_retrieveRetrieve the current API keyARead-onlyIdempotent
Retrieve the current API key
Use this call to check that your key works and how many calls are left today. It needs no scope.
Inputs: no named parameters.
open_requests_createCreate an open transport requestA
Create an open transport request
Posts a transport request that carriers on ESGO see. ESGO matches it against existing trips right away and against every new trip later. Counts against the daily quota "open_requests_create". Not retried automatically: a repeated call creates a second request.
Required API key scope: open_requests:write.
Inputs: origin (required), weight_kg (required), cargo_type (required), destination (required), +6 more.
open_requests_list_matchesList matches of an open requestARead-onlyIdempotent
List matches of an open request
Trips ESGO has matched to one of your open requests, best first. Reading them does not mark them as seen in the dashboard.
Required API key scope: open_requests:read.
Inputs: request_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
matches_search and open_requests_list_matches both concern 'matches', which could cause some initial confusion, but the descriptions clearly separate proactive capacity search from listing matches of an existing request. me_retrieve and open_requests_create are unambiguous.
All names follow a consistent snake_case resource_action pattern (matches_search, open_requests_create, open_requests_list_matches, me_retrieve). Minor deviation: 'me_retrieve' and the compound action 'list_matches' break the clean resource_verb rhythm slightly, but the convention is still predictable.
Four tools is a lean but coherent set for a focused transport-matching API, covering auth check, capacity search, request creation, and match retrieval. It's on the thin side but each tool earns its place with no obvious filler.
The surface covers search, create, and match-listing, but there is no way to list one's own open requests, retrieve a single request, or update/cancel an existing request. These are notable lifecycle gaps for a request-management domain, though core workflows are usable.
Maintenance
Related MCP Connectors
Geocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools.
Routing, geocoding, places, matrix and map tools for location-aware AI workflows.
Metered pay-per-call gateway for AI agent tools: search, discover, and call with one key.
Read-only search of 2,189 AI agent tools (MCP servers, x402 APIs) with daily automated trust scores.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceFreight marketplace MCP server for European road logistics. Search and manage freight loads, post truck capacity, create auctions, manage deliveries and drivers through the Cargoffer Bolsa de Carga API. Connect your AI agent to the freight marketplace.1MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to query and manage logistics shipment data, supporting operations like tracking, quoting, and performance analysis via nine tools backed by a demo dataset or a REST API.9253 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with SmartRoutes route optimization and dispatch tools, allowing users to manage orders, vehicles, and plans via natural language.MIT
- AlicenseNot gradedqualityBmaintenanceProvides real-time freight tracking and load visibility for logistics and AI agents: create loads, get live GPS positions, trip stats, and confirm deliveries via geofenced statuses.1MIT