Your AI assistant can now quote and track Ecoparcel shipments

Ask Claude what it costs to send a 2 kg parcel from Vilnius to Berlin, and it will tell you: €13.03, door to door, roughly 96 hours. Not an estimate it invented, not a number scraped off a comparison site last spring. That's our live pricing, the same figure the website would show you, fetched the moment you asked.

Ecoparcel now runs a Model Context Protocol server. If you use Claude or ChatGPT, you can connect your Ecoparcel account to it and ask about shipping the way you'd ask a colleague who happens to have the dashboard open.

Six things, as of today. You can get a price for any route we serve, with the transportation type and parcel dimensions you specify. You can track a parcel by its order code or parcel code and get the real event history back, not a «your item is in transit» placeholder. You can list your recent orders, filtered by status if you want only the ones sitting unpaid. You can pull the full detail of any single order, and you can download its shipping label as a PDF without opening a browser tab.

What you can't do yet is create an order or pay for one. That's deliberate, and we'd rather say so plainly than let you discover it mid-conversation. An assistant that can spend your money needs a confirmation step designed properly, not bolted on because the API happened to allow it. We're building that next, with an explicit approve-or-decline prompt before anything is booked. Until then the connector reads; it doesn't buy.

Add https://www.ecoparcel.eu/mcp as a custom connector, log in with your normal Ecoparcel account, approve the permission screen. That's the whole setup. There's no API key to generate, nothing to paste into a config file, no support ticket. You're logging in on our site, not typing your password into someone else's product, and you can revoke the connection whenever you like.

The permission you're granting covers quotes, tracking and reading your own orders. Nothing else. Your assistant sees your shipments and no one else's, because the token it holds is tied to your account specifically.

Most shipping integrations assume a developer on the other end: read the docs, write the client, handle the auth flow, maintain it. That's fine when you're wiring up a warehouse system. It's absurd overhead when you just want to know whether a pallet to Rotterdam beats a courier, or which of last week's fourteen parcels hasn't moved.

Our customers already spend their day in chat tools. The gap was that those tools had no way to reach real shipping data, so they'd either refuse to answer or make something up. Now they can ask us.

Being early here is partly luck of timing. The MCP authorization spec was revised on 28 July, the day before we went live, and we ended up implementing against a standard that was still warm. Some of it we got wrong first: our own rate limiting locked out the registration step, and a token audience rule rejected perfectly valid credentials for a few hours. Building on a spec this new means finding the sharp edges yourself.

We believe we're among the first shipping companies to offer this, though we haven't audited every competitor.

If you connect it and something behaves strangely, tell us. It's new, and the interesting bugs are the ones we haven't hit yet.