01What is SiteGiant MCP
MCP (Model Context Protocol) is an open standard that lets AI assistants use outside tools and data. SiteGiant MCP gives your AI assistant read-only access to your store's orders. Once it is connected, the assistant finds the available tools by itself, and you simply ask your question.
It works with AI assistants that let you add an MCP server with a custom header, such as Claude Code, Cursor and Codex.
02What it can do
SiteGiant MCP currently supports:
Query orders
- Search orders by date, status, sales channel or warehouse
- Look up an order by its SiteGiant order ID or its marketplace order number
- Get full order details: items, customer, addresses, payment and shipping
- Get package and tracking details
Everything is read-only. The assistant cannot create, change or delete anything in your store.
03Before you start
You need three things:
- At least one store connected to your account. The store owner gives you their store email and secret key, which they find on the API page of their SiteGiant ERP. Log in, open Stores and enter them under Connect a store. MCP only reaches stores that are connected this way.
- MCP access switched on for your account. It is off by default. To request it, contact SiteGiant support at support@sitegiant.my.
-
An MCP token for the store. Once MCP is switched on, log in, open
MCP Access in the menu and click Generate token beside the store. The token starts with
sgmcp_and is shown only once, so copy it straight away. Each store has its own token, and it is different from your Open API access token.
Keep your MCP token private. Anyone who has it can read your store's orders. If it is ever exposed, generate a new one on the MCP Access page; the old token stops working immediately.
04Connect your AI assistant
The connection details are the same for every assistant:
https://mcp.sitegiant.co/mcpAuthorization: Bearer YOUR_MCP_TOKENor, in the Claude app,
X-API-Key: YOUR_MCP_TOKEN
In the examples below, replace <name> with a name of your choice for this connection, such as the store's name
(letters, numbers and hyphens, no spaces), and replace YOUR_MCP_TOKEN with your own MCP token.
For the Claude app on the web or desktop. No file to edit: you add SiteGiant as a custom connector.
- In Claude, open Settings, then Connectors, and choose Add custom connector.
- Give it a name you will recognise, such as the store's name.
- For the server address, enter
https://mcp.sitegiant.co/mcp - For sign-in, choose No sign-in. Your MCP token is the login, so there is no account to sign in to.
-
Add a request header. Pick the name
X-API-Keyfrom the list and paste your MCP token as its value, on its own, without the word "Bearer". - Save, then start a new chat and ask: "Which SiteGiant store are you connected to?"
If Claude says it could not register with a sign-in service, the connector is not set to No sign-in. Change that option and try again.
For ChatGPT and the Codex app. These do not take a token: you sign in to SiteGiant instead, so you do not need to generate an MCP token for them. Custom connectors need a ChatGPT plan that includes them, with developer mode switched on in ChatGPT's settings.
- In ChatGPT, open Settings, go to the connectors (apps) section and choose to add a custom MCP server.
- Give it a name you will recognise, such as the store's name.
- For the server URL, enter
https://mcp.sitegiant.co/mcp - For authentication, choose OAuth, then create the connector.
- A SiteGiant page opens. Log in with your partner account.
- Pick the store this connection is for and click Allow access. You are taken back to ChatGPT.
- Start a new chat and ask: "Which SiteGiant store are you connected to?"
One connection is for one store. For another store, add the connector again and pick that store. To remove a connection, open MCP Access in your SiteGiant account and click Disconnect beside it.
- Open a terminal and run:
claude mcp add --transport http <name> https://mcp.sitegiant.co/mcp --header "Authorization: Bearer YOUR_MCP_TOKEN"
- Start a new Claude Code session.
- Type
/mcpand check that the name you chose shows as connected.
You can also add it to a .mcp.json file in your project folder:
{
"mcpServers": {
"<name>": {
"type": "http",
"url": "https://mcp.sitegiant.co/mcp",
"headers": {
"Authorization": "Bearer YOUR_MCP_TOKEN"
}
}
}
}
-
Open or create the file
~/.cursor/mcp.json(for every project), or.cursor/mcp.jsoninside one project folder. - Add:
{
"mcpServers": {
"<name>": {
"url": "https://mcp.sitegiant.co/mcp",
"headers": {
"Authorization": "Bearer YOUR_MCP_TOKEN"
}
}
}
}
- Save the file, then check that the name you chose appears in Cursor's MCP settings.
- Open the file
~/.codex/config.toml. - Add:
[mcp_servers.<name>]
url = "https://mcp.sitegiant.co/mcp"
http_headers = { "Authorization" = "Bearer YOUR_MCP_TOKEN" }
- Save the file and restart Codex.
Any assistant that supports a remote MCP server with a custom header can connect.
Most accept a configuration like this. Some call the type streamable-http and others http:
{
"mcpServers": {
"<name>": {
"type": "streamable-http",
"url": "https://mcp.sitegiant.co/mcp",
"headers": {
"Authorization": "Bearer YOUR_MCP_TOKEN"
}
}
}
}
If your assistant cannot set an Authorization header, send the token on its own in a header named
X-API-Key, Api-Key or MCP-Token instead. If you are unsure where the configuration goes, ask the assistant itself:
"How do I add a remote MCP server with a custom header?"
There are two ways to connect, and both reach the same data: paste a store's MCP token as a request header, or, for assistants that only offer a sign-in (OAuth) such as ChatGPT, sign in to SiteGiant and pick the store.
Connecting more than one store
Each store has its own token, so add each store as its own entry. The server address is the same for every store; only the entry's name and the token are different. Give each entry a name you will recognise, such as the store's name.
{
"mcpServers": {
"sitegiant-store-a": {
"type": "http",
"url": "https://mcp.sitegiant.co/mcp",
"headers": {
"Authorization": "Bearer TOKEN_OF_STORE_A"
}
},
"sitegiant-store-b": {
"type": "http",
"url": "https://mcp.sitegiant.co/mcp",
"headers": {
"Authorization": "Bearer TOKEN_OF_STORE_B"
}
}
}
}
In the Claude app, add one custom connector per store, each with its own name and that store's token in the X-API-Key header.
In Claude Code, run the add command once per store, with a different name each time:
claude mcp add --transport http sitegiant-store-a https://mcp.sitegiant.co/mcp --header "Authorization: Bearer TOKEN_OF_STORE_A" claude mcp add --transport http sitegiant-store-b https://mcp.sitegiant.co/mcp --header "Authorization: Bearer TOKEN_OF_STORE_B"
- When you generate a token on the MCP Access page, the configuration shown there already has the store's name filled in, so you can paste it as it is.
- Two entries must not share a name, or one replaces the other.
- Say which store you mean when you ask, for example "yesterday's orders for store A". You can also ask about several stores in one question.
- Connect only the stores you are working with. Each connected store adds to what the assistant has to keep track of, so a long list makes it slower and less accurate.
05Check that it works
Start a new conversation and ask:
The assistant should list the order tools enabled for your account and name the store the token is for. If it does, you are connected. If not, see Troubleshooting.
06Example questions
Give a date or a date range when you ask about a list of orders. The assistant needs one to search.
07Limits
These limits keep the service fast for everyone.
For a period longer than 30 days, the assistant searches it in several parts. If a request limit is reached, the assistant is told how many seconds to wait, and it works again after that.
08Good to know
- One token, one store. Put a store's token in your assistant and it works with that store, with nothing else to set. To use several stores, see Connecting more than one store.
- Dates are calendar dates in your store's own time.
- Your data and your AI provider. Order details the assistant reads, including customer names and addresses, are sent to the AI service you use. Check that this fits your own privacy obligations.
- Order text is written by buyers. Notes, names and addresses in an order are typed by customers, and an assistant can mistake such text for an instruction. SiteGiant MCP cannot change anything, but if your assistant also has tools that send email, post messages or browse the web, review what it is about to do before you approve it.
- Unused tokens expire. A token that is not used for 90 days stops working. Generate a new one on the MCP Access page.
- Check important figures. AI assistants can make mistakes when adding up long lists. For figures you will rely on, confirm them in SiteGiant.
- Your Open API access token does not work here. Use the MCP token only.
09Troubleshooting
Authorization: Bearer ... header in your configuration.sgmcp_. An Open API access token will not work.Still stuck? Email support@sitegiant.my with the message you see. Do not include your MCP token in the email.