How to connect Claude or ChatGPT to your Egyptian store stack in minutes

The question every operator is asking now

You have Claude, ChatGPT, or Cursor open all day. You've watched it write code and draft replies. The obvious next thought: "Can it just create my Bosta waybills? Reconcile Paymob? Issue my ETA receipts?" Then you look at what that takes — API keys for four services, webhook handlers, a server to run them on, someone to maintain it — and you close the tab.

The honest answer is yes, your agent can do all of that, and the work to get there is much smaller than the wall you just hit.

What the Wassel MCP endpoint is

MCP (Model Context Protocol) is the standard way an AI agent calls outside tools. Claude, ChatGPT, and Cursor all speak it. Wassel is one MCP endpoint that, once connected, gives your agent a set of regional tools: create a Bosta waybill, fetch Paymob settlements, issue an ETA Egypt e-receipt, send a WhatsApp Cloud message, read a Shopify order, push fulfilment to Salla or Zid.

You connect once. You do not write a separate integration for Shopify and another for Bosta and another for Paymob. The endpoint is the integration, and the agent is the logic.

Connecting it, concretely

1. Create a Wassel account and copy your endpoint URL and key from the dashboard.
2. Add it to your agent. In Claude Desktop or Cursor that's a few lines in the MCP config. In ChatGPT it's a connector. The dashboard shows the exact snippet for each.
3. Add the credentials for the services you actually use — your Shopify store, your Bosta API key, your Paymob private key. You only connect what you need; an agent that just creates waybills doesn't need your Paymob key.

That's the whole setup. Five to ten minutes if your API keys are handy.

What you can do once it's connected

Now the agent talks to your stack in plain language. Real instructions operators give on day one:

Pull every Shopify order from yesterday that's still unfulfilled and create a Bosta waybill for each one with the COD amount.

For order 18602, issue the ETA e-receipt through Wafeq and WhatsApp the customer the QR.

List Paymob settlements from last week and tell me which Shopify orders don't have a matching transaction.

No screen to learn. You ask, the agent calls the right Wassel tools in order, and reports back what it did. When you want it to run on its own — every paid order, every morning — you say that, and it runs on the trigger instead of waiting for you to ask.

Why this beats writing the integration yourself

1. One connection, not five. Bosta, Paymob, Shopify, ETA, and WhatsApp each have their own auth model and quirks. Wassel absorbs that. You connect once and the agent gets all of them.
2. No server to babysit. There's no integration service of yours that goes down at 2am. The endpoint is hosted; your agent calls it.
3. The logic is a sentence, not a codebase. New courier, new tax rule, new message — you change the instruction. There's no deploy.
4. Time and money. A custom Shopify-to-Bosta-to-Paymob integration is weeks of developer time, call it 40,000 to 120,000 EGP to build and someone to maintain it. Connecting an MCP endpoint is an afternoon.

Point your agent at the endpoint

Open the Wassel dashboard, copy the MCP endpoint, and paste it into your Claude, ChatGPT, or Cursor config. Connect your Shopify store and one courier key to start. Ask it to create a waybill for a single test order before you let it loose on the full queue.

If a tool you need isn't in the list yet, tell us what API and we'll prioritise it off real operator asks, not a roadmap.