Let Claude, Cursor, VS Code, and other MCP-compatible AI agents manage your store data — no integration code required.
AI agents need real data to be useful
AI agents are getting good at reasoning. But they have been missing safe, structured access to real business data. The new API2Cart MCP Server closes that gap for e-commerce.
You can now connect AI agents and assistants — Claude, Cursor, VS Code, OpenAI Codex, Google Antigravity, LM Studio, or any other MCP-compatible client — directly to your API2Cart account. The agent talks to your stores through the same unified API you already use. So you can ask it, in plain language, to look up orders, update products, or manage customers, without writing a line of integration code.
You will find the new MCP settings page under Settings > MCP in your dashboard.
Access tokens you control
You can generate one or more tokens, each with its own label, so you always know which agent or workflow it belongs to. You also choose a lifetime — 1 hour, 8 hours, 24 hours, 7 days, 30 days, or a custom duration up to 180 days.
Fine-grained access control
Every token is scoped independently. So an agent only ever sees what you allow:
- Restrict a token to specific store connections, or leave it open to all of them
- Pick exactly which integrations the token can work with
- Pick exactly which API methods it is allowed to call
- Optionally hide raw connection keys from the agent entirely — it then references connections only by ID, and keys never appear in tool parameters or responses
One-click client setup
Click Connect an MCP client next to any token. You get a ready-to-use config snippet, pre-filled with your token and the correct server endpoint, for Claude Code, Cursor, VS Code, OpenAI Codex, Google Antigravity, and LM Studio. Paste it into your client config, and you are connected.
A toolset that stays out of the way
The set of tools an agent sees is dynamic. A new session starts with a minimal toolset — just enough to list, add, and select connections. Once the agent picks an integration or an existing connection, the server loads only the tools for that platform. So no agent ever gets flooded with hundreds of irrelevant tools.
It works even with small local models
Because the toolset stays compact, the MCP server is not limited to large cloud models. We tested it with small local LLMs like Gemma 4 12B (Q4). Even at that size, the model can use the tools, connect stores, and work with product catalogs without issues.
Built with safety in mind
Tokens authenticate over a standard Bearer header. Treat them like passwords. A token restricted to specific connections cannot reach anything outside that scope, and it cannot add new connections either.
Getting started
- Open Settings > MCP in your API2Cart dashboard
- Click Generate New Token, name it, and choose a lifetime
- Optionally restrict it to specific connections, integrations, and methods, and enable hide connection keys for extra protection
- Click Connect an MCP client and copy the config into your client of choice
That is it — your AI agent now speaks directly to your store data.
