Skip to main content
Connect TWICE Docs to your AI tool and ask it how TWICE Commerce works. To have the tool run tasks on your account through the Admin API, also give it an API key.

Ask TWICE Docs from your AI tool

Add https://www.twicecommerce.com/docs/mcp to your tool as an MCP server. It needs no sign-in and no API key.
1

Add a custom connector

Open the Connectors page in the Claude settings and select Add custom connector.
2

Configure TWICE Docs

Enter these details, leave Authentication at No sign-in, and select Add:
  • Name: TWICE Docs
  • URL: https://www.twicecommerce.com/docs/mcp
3

Turn it on in a chat

Open the attachments menu (the plus icon) and select TWICE Docs.
Ask anything you would look up in these docs, in your own words and language:
  • “How do I add a new location and set its opening hours?”
  • “Why can’t customers order this listing?”
  • “How do I fetch orders changed in the last 45 days through the API?”
The tool answers with TWICE Commerce’s own steps and admin paths, such as Settings → Locations, and links the pages it used. For the API question, a correct answer pages through GET /v1/admin/orders/list and sends filters as one JSON-encoded parameter with an updatedAt filter and "scope":"all".

Let your tool work on your account

Give Claude Code, Cursor or VS Code an API key, and the tool calls the TWICE Commerce Admin API for you: it fetches orders, changes stock, creates listings. The tool sends each request itself, from your computer, with the key you set there.
1

Create the key

Open Settings → Integrations & API and press Create key in the API keys section. Enter an API key label that names the tool, such as Cursor – Anna, and pick when the key Expires.
2

Give it only the areas your tasks need

Under Access, pick Limited access and set each area your tasks need to Read or Write. Run a task lists the areas per task. Start with Read, and add Write when you want the tool to change data.
3

Copy the key

Press Create API key and copy the key. The full value is shown once.
4

Set the key where the tool runs commands

Set it as the TWICE_API_KEY environment variable, as shown below for your tool.
Keep the key out of the chat and off the TWICE Docs connector. A chat is stored with your AI provider. A header on the connector goes to the docs server, which does not use it. A key with Write access changes your account.
Add the key to .claude/settings.local.json in your project. Claude Code keeps this file out of git and sets the variable for every command it runs:
Restart claude after you save the file.
To keep the key across Cursor and VS Code sessions, add the export line to your shell profile (~/.zshrc or ~/.bashrc), or set it as a user environment variable on Windows. Check the connection with a key that holds Catalog → Listings at Read. Ask: “Use the API key in TWICE_API_KEY to count my listings with GET /v1/admin/catalog.” The count matches Catalog → Listings in the admin.

Run a task

Name the job and where the key is. The tool reads the matching skill from TWICE Docs, calls the API and checks the result:
Use the TWICE Commerce API key in TWICE_API_KEY. Fetch my orders changed in the last 7 days and list them by status.
Read each request the tool proposes before you approve it. The twicecommerce skill holds the conventions every call shares: authentication, scopes, query encoding, pagination, amounts, errors and rate limits. Each skill names the endpoint to use, the ones to avoid and how to verify the result, and carries the date it was last checked against the production API. Over MCP, your tool reads the skills as resources. To install them into a tool that reads skill files instead, run npx skills add https://www.twicecommerce.com/docs.

Troubleshooting / common pitfalls

The TWICE Docs server is not on in this conversation. In Claude Desktop, select TWICE Docs in the attachments menu. In Claude Code, run /mcp and check that twice-docs is connected.
The tool cannot run commands, or it is in a mode that only chats. Use Claude Code, or Cursor or VS Code in Agent mode. In Claude Desktop, ask the tool to write the request and run it yourself.
The tool sent no key, a wrong one, or an expired one. Ask the tool to print the first four characters of $TWICE_API_KEY. If it prints nothing, set the variable again and restart the tool. An expired key returns “This API key has expired”. Replace it with Duplicate on the key’s row.
The key does not hold the area the request needs. The response’s details.requiredScopes names the scopes that would open it. Add one of them to the key under Edit access. The change applies within five minutes.
The tool has not read the skill. Ask it to read the resource mintlify://skills/sync-orders from TWICE Docs and try again. The URI works even when your tool does not list the skill.
Tell your tool to submit feedback through the TWICE Docs connection, naming the page or skill that sent it the wrong way. The feedback goes to the docs team.

API keys

Every area a key can reach, expiry, and the rate limits.

Integrations settings

Create, edit and delete API keys.

Webhooks

Receive order events as they happen.

OS approach

How TWICE Commerce approaches MCP and the agent-facing platform.