API2Cart MCP

To connect an MCP client, create an MCP access token first.
- Log in to the API2Cart dashboard.
- OpenSettings -> MCP.
- ClickGenerate New Token.
- Enter a token label, for examplelocal agentorCursor workspace.
- Select the token lifetime.
- Optionally restrict the token by integrations, API methods, connection ids, or the hide connection keys option.
- ClickGenerate Token.
- Copy the token and endpoint.

The token is passed to the MCP client through the HTTP header:

The MCP token gives access to API2Cart MCP tools within the permissions selected during token generation.

One account can have up to 5 active MCP tokens. Expired tokens are deleted automatically. The maximum token lifetime is 180 days.

It is recommended to create a separate token for each AI client or workspace.
- Allowed integrations- the agent sees only selected e-commerce integrations.
- Allowed API methods- the agent can call only enabled methods.
- Connection IDs- the agent can work only with specific connections.
- Hide connection keys- the agent uses connectionidvalues and does not see rawstore_keyorconnection_keyvalues.

If a token is restricted to specific connection ids, the agent cannot add new connections because the new connection is not yet in the whitelist.

IfHide connection keysis enabled, tools that directly change raw keys through parameters such asnew_store_keyornew_connection_keymay be unavailable to the agent.

To connect an MCP client, follow these steps:
- OpenSettings -> MCP.
- Find the required token in the token grid.
- ClickConnect.
- Select your MCP client.
- Copy the generated command or config.

claude mcp add --transport http api2cart https://mcp.api2cart.com/ --header "Authorization: Bearer YOUR_MCP_TOKEN"

After the MCP client is connected, it receives the API2Cart guidance and available tools automatically. Users do not need to run internal tools or manage the toolset manually.

API2Cart stores the selected integration and active connection in a server-side session. When the agent switches integrations or adds a new connection, the available tools are updated automatically. Some MCP clients may need a few seconds to display the updated toolset.

If the client loses its local conversation context, the API2Cart session may remain active. The agent can continue working with the selected connection. To restore context, provide the connectionid; rawstore_keyorconnection_keyvalues are not needed for an existing connection.

When you ask the agent to work with a connection that already exists in API2Cart, it finds the available connections, identifies the relevant integration, and selects the connection:

find connection -> select integration -> select connection -> use platform tools

After selecting the connection, the agent uses integration-specific tools, such as product, order, category, customer, shipment, refund, or webhook tools.

If you already know the connectionid, include it in your request. This lets the agent restore the required connection without asking for raw credentials.

One platform can have multiple integrations. For example, WooCommerce can be available as an API-based integration and as a bridge-based integration. Magento can also have separate API-based and bridge-based options.

To choose the right integration, the agent uses these fields:
- integration_id- technical identifier forselect_integrationandadd_connection.
- name- display name.
- connection_method- API-based or bridge-based.
- versions- supported platform versions.

API-based connections work through the platform API and require API credentials. Bridge-based connections work through API2Cart bridge or connector on the store side and may require a bridge key, FTP/SSH access, or plugin installation.

If it is unclear which option to use, ask the agent to compare the required credentials for the available integrations.

When you ask the agent to add a new connection, it identifies the available integrations, checks the required parameters, and asks only for the credentials needed by the selected platform:

find integration -> check required parameters -> add connection -> verify connection

After a successful connection, the new connection is activated automatically and the agent verifies its details. If a platform has multiple integrations, you can specify the preferred connection method, such as API-based or bridge-based.

The shared demo store can be visible in the connection list, but it is not accessible for MCP tool calls. If the agent selects a demo connection, API2Cart MCP returns an explicit error. For real work, connect your own store throughadd_connectionor use an existing non-demo connection.

Use API2Cart MCP. Work with connection id 12345 and get the first 10 products with id, name, sku, price, and image URLs only.

Use API2Cart MCP. Work with my selected connection. Get orders updated during the last 24 hours. Return only order id, status, total, currency, customer email, and updated time.

Use API2Cart MCP. I want to connect a Shopify store. Show the required connection parameters first. Ask only for credentials that are required by the selected integration.

- Create separate MCP tokens for different clients or projects.
- Use a short token lifetime for testing.
- Restrict the token to required integrations and methods when possible.
- Use Connection IDs restriction for production-sensitive accounts.
- Enable Hide connection keys if the AI agent should work only with connection ids.
- Do not paste MCP tokens into chats, tickets, logs, screenshots, or shared documents.
- Delete tokens that are no longer used.

To revoke access immediately, openSettings -> MCP, find the token in the token grid, and delete it. Revocation takes effect immediately: any MCP client using that token loses access on its next request, and cached sessions tied to the token are invalidated.

API2Cart creates one audit log record for each HTTP request to the MCP endpoint. The record includes the request time, called tool name, response status, and execution duration.

Account logs are available in the dashboard atDashboard -> MCP Logs. The logs are scoped to your account. To investigate a problem, use the request time and tool name, then check the response status and duration.

TheAuthorizationvalue and credentials fromadd_connectionare redacted before storage. The MCP audit log does not store the response body, so it helps diagnose errors and slow requests but is not an archive of complete API responses. Older records are removed automatically according to the log-rotation policy.

The client is connected, but no API tools are visible

Some MCP clients need a few seconds to display an updated toolset. If the tools do not appear, ask the agent to refresh the MCP session or start a new client turn.

Check that the correct integration is selected and that the MCP token allows the required methods. If the client was connected recently, wait a few seconds for the toolset to update.

The MCP token was generated with restrictions. Open Settings -> MCP and edit the token permissions, or create a token that allows the required method.

The agent asks for store_key or connection_key

Provide the connectionidor ask the agent to find the connection in your API2Cart account. Do not provide raw keys unless you are intentionally adding a new connection and the selected integration requires them.

Ask the agent to return only the required fields, use a smallercount, or narrow the date or filter range.

Discover how API2Cart can ease your eCommerce integrations with a personalized demo. See how seamlessly our solution can connect your software with over 70 eCommerce platforms.

Don't miss out!This is an exclusive one-time offer. Secure your additional trial period by booking your demo now.

Manage your Jumpseller e-commerce store with AI. Create products with variants, process orders, search customers, and organize your catalog.

D2C eCommerce fulfillment platform: manage orders, inventory, shipments, campaigns, and billing via AI agents

Provides real-time tracking for 1,300+ carriers and merchant returns center demos with no API key required, using AfterShip's MCP server. Powered by AfterShip.

Manage products, orders, and customers on Color Me Shop

Access the KiotViet API, a popular sales and inventory management platform. Manage products, categories, customers, and orders with automatic authentication.

Agent-native Ops OS for ecommerce and retail — CRM, orders, inventory, fulfillment, shipping, omnichannel messaging, and AI analytics. All through a single MCP connection.

Integrates with the Shopify API to retrieve and manipulate product information.

Give your AI a direct line into your Swell store. Manage products, orders, and customers through natural conversation.

Transaction-complete hotel booking over MCP — 300K+ properties, real hotel confirmation numbers, loyalty points, secure checkout. Hotels are merchant of record. Builders set their own booking fee via Stripe Connect. Built on proven distribution infrastructure.