1. Connect with just the server URL (recommended)
Most MCP clients connect with only the Sirdab MCP URL, no token to copy.
In your MCP client, add a custom connector / server with the URL:
https://partner.sirdab.app//mcp.The client discovers how to sign in automatically (it reads Sirdab's OAuth
discovery documents from the `WWW-Authenticate` hint on the first `401`).
Your browser opens the Sirdab portal: **log in and approve access.**
The client receives a token and connects. Access is scoped to your organization and your portal role, so the tools see exactly what you see in
the portal.
Any client, no pre-registration: your MCP client registers itself
automatically (RFC 7591 Dynamic Client Registration) and declares its own
callback URL, so claude.ai web, Claude Desktop, MCP Inspector, Cursor, and VS Code all work. Loopback callbacks (`http://127.0.0.1:<port>/…`) are supported for
native/CLI clients.
2. What the agent can do (tool catalog)
Every result is scoped to your organization and the user's role.
Read tools fetch data; **write** tools create or change it. You don't call these by hand: the agent picks the right tool from your request.
Model | Read | Write |
Orders (Fulfillment Orders) | `list_orders`, `get_order` | `create_order`, `cancel_order` |
Fulfillment customers | `list_fulfillment_customers`, `get_fulfillment_customer` | `create_fulfillment_customer`, `update_fulfillment_customer` |
Outbounds | `list_outbounds`, `get_outbound`, `get_outbound_skus` | `create_outbound`, `update_outbound`, `cancel_outbound`, `submit_outbound`` `add_to_cart`, `edit_quantity`, `update_sku`, `remove_sku` |
SKUs & inventory | `list_skus`, `get_sku`, `get_inventory` | `create_sku`, `edit_sku`, `archive_sku`, `unarchive_sku` |
Inbounds | `list_inbounds`, `get_inbound` | `create_inbound`, `update_inbound`, `cancel_inbound` |
SKU groups | `list_sku_groups`, `get_sku_group` | `create_sku_group`, `update_sku_group`, `delete_sku_group`, `add_user_to_sku_group`, `remove_user_from_sku_group`, `add_sku_to_sku_group`, `remove_sku_from_sku_group` |
Warehouses | `list_warehouses`, `get_warehouse`, `get_warehouse_capacity`, `get_warehouse_time_slots` |
|
Quotes | `list_quotes`, `get_quote` | `init_quote`, `update_quote`, `approve_quote` |
Addresses & suppliers | `list_addresses`, `get_address`, `list_suppliers` | `create_address`, `update_address` `create_supplier`, `update_supplier` |
Reports | `list_reports` | `create_report`, `delete_report` |
Lookups (for ids) | `list_carriers`, `list_cities`, `list_categories` | - |
Integrations | `list_integrations`, `list_connected_integrations` | - |
EX: how to create a Fulfillment order using the MCP ?
in your AI Agent (Claude) , type "I need to create an order in sirdab" then
it will start ask you some questions about the address and needed skus and the customers , payment method and delivery option ..etc
https://drive.google.com/file/d/1gB3e1cQIyQ-G6yu5yNXPunDlnf-Uri1u/view
3.Manage connected apps
Under **Settings → Developer → Connected apps** you can see every AI client
connected to your account (name and connected date) and **Disconnect** any of them.
Disconnecting cuts off that client's access immediately: its next request is
rejected (401).
You can also remove the connector from inside your AI client (it revokes its own
access).
You only ever see and manage **your own organization's** connections.
4. Notes & troubleshooting
Data scope: you only ever see your own organization's data; a user's role can narrow it further (the same rules as the Sirdab merchant portal).
401 Unauthorized: the token is missing, revoked, expired, from the wrong
environment, or not a `merchant_portal` token. Reconnect (section 1) or mint a
fresh token (section 2).
406 / Not Acceptable: the `Accept: application/json, text/event-stream`
header was dropped.
Empty results: the account genuinely has no matching records, or your `search`
filtered them all out.
Write tools change your data. They go through the same validation as the
merchant portal, so an invalid request comes back with a clear error instead of a partial change. Destructive actions (cancel/delete) run when you ask; your client (e.g. Claude) confirms the tool call before it executes.