Waypoint MCP
Connect your Waypoint account to Claude or any AI client that speaks MCP, and ask about stock, orders and returns without signing in to anything.
Anything that supports the Model Context Protocol. One connection, and it stays connected.
Three steps, once. Nothing to copy and no key to paste — you sign in with the Waypoint account you already have.
In Claude that is Settings → Connectors → Add custom connector. Leave the optional OAuth fields blank; your client registers itself.
https://mcp.waypoint3pl.com
You are sent to Waypoint to sign in, then shown exactly what the connection will be able to see. Choose Sandbox the first time — it can only ever read test data, so there is nothing to get wrong while you are trying it.
Using a client that reads a config file? Cursor, VS Code and
claude mcp add can send an API key directly instead, as
Authorization: Bearer wp_test_…, using a key from your portal under
API & Integrations. Both routes reach the same place.
Everything it knows comes from your account, live, at the moment you ask.
What is on the shelf, what is allocated to orders that have not gone yet, and what has fallen below the level you set.
Where one order is, what is in it, where it is going, and the tracking number once it has left us.
Which orders are still with us, what shipped this week, what was cancelled, what came back.
What came back, in what condition, and whether it went back into sellable stock.
The services available to your account, their weight limits, and what each costs you.
The full specification, so an AI writing an integration against us works from the real thing rather than a guess.
Ordinary questions, in ordinary words. It works out which to look up.
That is a deliberate choice rather than a feature we have not built yet. An assistant decides for itself when to use a tool — nobody presses a button — and the consequences are not symmetrical. Reading the wrong order wastes a moment. Cancelling the wrong one stops a real parcel that a real person is waiting for. Anything that changes an order stays where a person does it: your portal.
No. Connecting signs you in to Waypoint and asks you to approve, the same as connecting any other account. Clients that read a config file rather than showing you a sign-in screen can use an API key instead, and both work.
No. It is part of your Waypoint account, like the API and the portal.
Yes — they are different jobs. The connectors move your orders to us and bring tracking and stock back, automatically, without anybody asking. This is for asking questions. It moves nothing.
Whatever comes back from a question you asked passes through your AI client, the same as anything else you type into it. If that matters for your customers' addresses, ask about stock and order status rather than pulling up full delivery details — and read your AI provider's own terms, because that part is between you and them.
That is what a sandbox key is for. It reads sandbox orders and sandbox stock only, and nothing it shows you has anything to do with your real warehouse.
Partly. It can hand your AI our full API specification while it writes the integration, which is better than it guessing. But if the shop runs on Shopify, WooCommerce or Magento, the right answer is to install the connector rather than build anything — it already handles the parts that are easy to get wrong.
Tell us rather than working around it: info@waypoint3pl.com. The portal is always the authority — if the two disagree, believe the portal.
This is one small part of it. The rest is a warehouse just outside London that picks, packs and posts your orders.