MCP Server

Overview

The Shirtigo MCP server lets an AI assistant work on your Shirtigo account: search the catalogue, calculate prices, look up, place and cancel orders, read and edit the products in your collections and push them into your connected shops, and read your balance and statistics.

It speaks the Model Context Protocol at a single endpoint:

https://cockpit.shirtigo.com/api/mcp

Which tools an assistant can see and call is decided entirely by the permissions on its token. tools/list only returns the tools those permissions cover, so an assistant never sees a tool it cannot use.

Authentication

There are two ways to authenticate, and both work at the same address.

OAuth

The usual way, and the one Claude and ChatGPT use. Enter the address above in your client. It discovers the rest on its own and registers itself, so there is no client id and no secret to manage. You then sign in with your Shirtigo account and tick the permissions the assistant should get. Connected assistants are listed on the AI assistants page, where you can disconnect one at any time.

Personal Access Token

For clients that do not speak OAuth. Create a token on the Integrations page, tick the scopes you want, and send it as a bearer token:

Authorization: Bearer YOUR_TOKEN

A Personal Access Token also works on the REST API. A token from an OAuth assistant connection does not; it is only accepted at the MCP endpoint.

Tools

Tool	Permission
search_catalog	valid token
get_base_product	valid token
calculate_product_price	valid token
calculate_order_price	valid token
list_orders	read-order
get_order	read-order
create_order	write-order + read-order-address
cancel_order	write-order
update_order_delivery_address	write-order + read-order-address
list_collections	read-project
get_collection	read-project
list_collection_products	read-project
get_collection_product	read-project
update_collection_product	write-project
sync_collection_product	write-project
sync_collection	write-project
list_shops	read-user
get_account_balance	read-user
get_sales_statistics	read-stats
get_action_required_statistics	read-stats

Every tool describes itself, its arguments and its answer to the assistant, so you do not have to teach it any of that. Three things are worth knowing before you call them:

• create_order places a binding order and costs money. It requires a confirmed_total taken from a preceding calculate_order_price call for the identical payload, and creates nothing if that amount no longer matches the current price.
• sync_collection_product and sync_collection overwrite a product that already exists in a shop, which discards edits made in the shop itself. Both require confirm_overwrite.
• read-order-address releases the addresses and the contact email of an order. Without it, order responses carry no personal data of your customers.

Every tool that returns a list takes limit and page. The default page size is 10, the maximum is 50.

Rate Limiting

The endpoint shares the throttle of the rest of the API: 60 requests per minute. An assistant that issues several tool calls per turn reaches that ceiling faster than a human clicking through the REST API, so expect 429 responses during heavy use.