A Model Context Protocol server that lets an AI agent order food and groceries on Chowdeck (Nigeria) — discover vendors, get meal suggestions, build a cart, place an order, and track delivery.
Built and maintained by Hendrix Nwaokolo (@thathman).
| Capability | Status |
|---|---|
| Browse vendors, menus, search, suggestions | ✅ Working |
| Guest & authenticated carts | ✅ Working |
| Phone-OTP login, profile, addresses, wallet | ✅ Working |
| Place & track orders | ✅ Working |
| Pay — returning customer with a connected (saved) card | ✅ Working (charges inline) |
| Pay — online payment / bank transfer (card-less & new customers) | 🚧 In progress |
Right now, ordering end-to-end only completes for existing customers who have a card already connected to their Chowdeck account. Online payment (bank transfer, card-less, and brand-new customers) reaches the Paystack hand-off but is not yet fully automated. See the Changelog for details.
This is an independent, unofficial project. It is not affiliated with, endorsed by, or supported by Chowdeck. It talks to Chowdeck's private storefront API the same way the official web app does. As a result:
- No credentials are bundled. You authenticate as yourself with your own phone + OTP, and supply your own Google Maps key (
CHOWDECK_MAPS_KEY) for reverse-geocoding. The project ships no API keys or tokens.- Respect Chowdeck's Terms of Service. Use it for your own account and personal ordering. Don't scrape, resell, automate abusively, or hammer the API — the client is rate-limit-friendly (timeouts, bounded retries) for that reason. You are responsible for your own use.
- It may break at any time. Because the API is private and undocumented, Chowdeck can change it without notice. Endpoints marked best-effort in the code are inferred and may need updating.
- Trademarks ("Chowdeck", "Paystack") belong to their owners and are used only to describe interoperability.
If you represent Chowdeck and would like changes, please open an issue.
flowchart TD
A[AI Agent / Claude] -->|MCP stdio| B[Chowdeck MCP server]
B --> C{Session on disk?}
C -- no --> D[First-time setup:\nphone OTP login + address]
C -- yes --> E[Reuse saved session]
D --> F[Detect new vs returning user]
E --> F
F --> G[Discover vendors & menus]
G --> H[Build cart]
H --> I[Quote delivery fee]
I --> J{Payment}
J -- saved card --> K[✅ Charged inline\nPIN + rider returned]
J -- online / transfer --> L[🚧 Hosted pay link\n→ Paystack hand-off]
K --> M[Track order]
L --> M
📌 A richer architecture/visualisation diagram will be added here later.
The server exposes 45 tools and 4 prompts, grouped by capability (request/response details are intentionally omitted from this README):
- Setup & session — persistent login + delivery address, automatic new-vs-returning customer detection, saved payment preference.
- Location — address autocomplete, place details, reverse geocoding (your
own
CHOWDECK_MAPS_KEY), and saving a precisely resolved delivery address. - Discovery — storefront config, vendor listings with filters (sort, open-now, min-rating, max-fee, free-delivery), featured/handpicked vendors, search, menu categories, menus, and individual menu items.
- Favourites — list, add, and remove saved vendors.
- Cart — create/update, list all, per-vendor view, clear, delete, and reorder from a past order.
- Auth — Nigerian phone-number OTP login and profile lookup.
- Account — saved addresses, wallet balance, order history, payment methods.
- Orders & checkout — delivery-fee quote, place order (with optional scheduled delivery, rider tip, and promo codes), live order tracking (status/ETA/PIN/rider), active orders, order detail, payment channels, payment start/verify, and wallet top-up.
Safety: every tool is hinted readOnly or destructive; money-moving and
data-loss tools (place_order, wallet_topup, clear_carts, delete_cart,
logout) require an explicit confirm: true and otherwise return a
"confirm with the user first" no-op. Large responses are slimmed to keep token
use low; get_session / get_setup_status return structured output.
Prompts: order_food, find_food_near_me, track_my_order,
reorder_my_usual.
Sessions persist to ~/.chowdeck-mcp/session.json (written 0600), so the
one-time login and address setup survive restarts.
chowdeck-mcp/
├── mcp/ # The MCP server
│ ├── src/
│ │ ├── index.ts # Tool definitions + server wiring (stdio)
│ │ ├── api.ts # Chowdeck API client
│ │ └── session.ts # Disk-persisted session store
│ ├── package.json
│ └── tsconfig.json
├── skill/
│ └── chowdeck/
│ └── SKILL.md # Claude/agent skill: how to drive the server
├── .github/
│ ├── workflows/ci.yml # Build + smoke-test on push/PR
│ └── FUNDING.yml # Sponsorship
├── CHANGELOG.md
├── LICENSE # MIT
└── README.md
- Node.js 20+ and npm
- A Nigerian phone number with a Chowdeck account (for authenticated flows)
git clone https://github.com/thathman/chowdeck-mcp.git
cd chowdeck-mcp/mcp
npm install
npm run buildNote: An MCP server is not "installed" like an app — it is registered with your agent/client as a command the client launches over stdio. You cannot simply tell a client to "install this repo"; point it at the built server (or at
npxonce published — see below).
Claude Code / CLI:
claude mcp add chowdeck -- node /absolute/path/to/chowdeck-mcp/mcp/dist/index.jsOpenClaw / generic MCP client (mcpServers config):
{
"mcpServers": {
"chowdeck": {
"command": "node",
"args": ["/absolute/path/to/chowdeck-mcp/mcp/dist/index.js"]
}
}
}Add that block to your client's MCP config (for OpenClaw, its MCP servers
settings), then restart the client. The agent will then see the chowdeck tools.
Published to npm as @thathman/chowdeck-mcp —
no clone or build needed; clients launch it directly:
{
"mcpServers": {
"chowdeck": {
"command": "npx",
"args": ["-y", "@thathman/chowdeck-mcp"],
"env": { "CHOWDECK_MAPS_KEY": "your-google-maps-key (optional, for reverse_geocode)" }
}
}
}The bundled skill/chowdeck/SKILL.md tells the agent
how to run first-time setup, branch on new-vs-returning customers, resolve an
exact delivery address, and always confirm the order (and announce the delivery
PIN + rider) before checkout.
- Your auth token, guest id, address id, phone, and payment preference live only
in
~/.chowdeck-mcp/session.jsonon your machine. Nothing is sent anywhere except Chowdeck's own API. - OTP codes and tokens are treated as secrets and are never echoed back in summaries.
- Run
logout(a tool) to wipe the saved session.
See CHANGELOG.md for version history and the current state of the online-payment work.
If this saves you time, consider sponsoring the project.
Licensed under the MIT License — free to use, copy, modify, and distribute (including commercially); just keep the copyright and license notice.
Built and maintained by Hendrix Nwaokolo (@thathman) / Airix Media. A credit or ⭐ is always appreciated.