getir-mcp
# getir-mcp
MCP server for Getir partner API (Turkey). Manage orders, products, pricing, and store status for your Getir restaurant via Bearer token authentication.
## Tools (8)
| Tool | Description |
|---|---|
| `list_orders` | List active/past/scheduled orders |
| `get_order` | Get order details by ID |
| `accept_order` | Accept an incoming order |
| `reject_order` | Reject an order with reason |
| `list_products` | List products in your store |
| `update_product_availability` | Enable/disable a product |
| `update_product_price` | Update product price |
| `get_store_status` | Get current store open/busy status |
## Quick Start
```json
{
"mcpServers": {
"getir": {
"command": "npx",
"args": ["-y", "@theyahia/getir-mcp"],
"env": {
"GETIR_TOKEN": "<YOUR_BEARER_TOKEN>"
}
}
}
}
```
## Environment Variables
| Variable | Required | Description |
|---|---|---|
| `GETIR_TOKEN` | Yes | Bearer token from Getir partner portal |
## Demo Prompts
- "Show me all active Getir orders"
- "Accept order ORD123 with 15 minute preparation time"
- "Reject order ORD456 because we are out of lahmacun"
- "Disable the Iskender product temporarily"
- "Update price of product P001 to 89 TRY"
- "Is my store currently open on Getir?"
## License
MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: orders (list, get, accept, reject), products (list, update availability, update price), and store status (get). No two tools overlap in purpose, so an agent can clearly distinguish them.
All tool names follow a consistent verb_noun pattern in snake_case: list_orders, get_order, accept_order, reject_order, list_products, update_product_availability, update_product_price, get_store_status. This makes the set predictable and easy to navigate.
With 8 tools, the set is well-scoped for a Getir store management server. It covers orders, products, and store status without unnecessary redundancy or bloat.
The tool set covers the core workflows for managing orders (list, get, accept, reject) and products (list, update price, update availability). However, there is no way to update store status (e.g., open/close), which is a minor gap in lifecycle coverage.