Appexbots can be connected to an AI assistant — Claude, ChatGPT, Cursor, Claude Code and any other client that supports MCP. The agent works with your bots, shop, catalog, orders and clients with the same rights you have in the admin panel: for example, "add 20 products from this price list", "translate the catalog into English", "show last week's orders and message the clients whose orders are delayed".
Connecting takes a couple of minutes: create an API key in the admin panel, download the config and paste it into your assistant's settings.
.json) or copy it. A lost key cannot be recovered, only replaced with a new one.The key is equivalent to your admin password within the selected scopes. Do not publish it or forward it in open chats. If a key leaks, revoke it in the same section — the agent loses access immediately.
The dialog of the created key and the downloaded config contain everything you need:
…/mcp/key/apx_… (with a toolset — …/mcp/key/apx_…/x/catalog) for clients that cannot send headers (Claude.ai, ChatGPT);mcpServers block — a ready-made config for Cursor, Claude Code, Claude Desktop, VS Code;Appexbots, Remote MCP server URL: paste the connector URL. Leave authentication empty — the key is embedded in the link.Appexbots, MCP Server URL: paste the connector URL, Authentication: No authentication.Use this when the whole team should share one GPT.
…/mcp/openapi-catalog.json).…/mcp/openapi.json has about 80, so GPT Builder rejects it — import groups as separate actions: …/mcp/openapi-catalog.json, …/mcp/openapi-orders.json, …/mcp/openapi-merchant.json, …/mcp/openapi-bots.json (the links are on the …/mcp/docs page).apx_… key.https://appexbots.com/privacy.claude mcp add --transport http appexbots https://app.appexbots.com/app/mcp --header "Authorization: Bearer apx_..."
The ready-made command with your key is in the config (field appexbots.claudeCode).
mcp.jsonCopy the mcpServers block from the downloaded config into the client's settings file (Cursor: ~/.cursor/mcp.json or Settings → MCP → Add; VS Code: .vscode/mcp.json, key servers):
{
"mcpServers": {
"appexbots": {
"type": "http",
"url": "https://app.appexbots.com/app/mcp",
"headers": { "Authorization": "Bearer apx_..." }
}
}
}
Clients that understand stdio only connect through mcp-remote:
{
"mcpServers": {
"appexbots": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://app.appexbots.com/app/mcp", "--header", "Authorization: Bearer apx_..."]
}
}
}
Files cannot be downloaded inside the Telegram browser: in the key dialog click Copy config and save the text on your computer, or open the admin panel in a regular browser.
The server exposes about 80 tools. Claude and ChatGPT cope with that, but small models (Qwen, Llama, GigaChat, 32k context) spend half of their context on the list and start mixing up parameters. Connect such an agent to a URL with the toolset it needs:
…/mcp/x/catalog — products, categories, pictures, translations;…/mcp/x/orders,crm — orders, chat, clients, promo codes, mailings;…/mcp/x/merchant,bots — shop and bot settings;…/mcp/x/reports — dashboard and reports;/readonly to hide every write tool: …/mcp/x/catalog/readonly.Toolsets can be combined with a comma; context tools (whoami, dictionaries) are part of every set. With the key in the link — …/mcp/key/apx_…/x/catalog; clients that can send headers may use X-MCP-Toolsets: catalog,orders and X-MCP-Readonly: true instead. A toolset only narrows the key's scopes: a tool outside the set returns a clear error saying which URL to connect to.
Errors come back to the agent as text: which argument is wrong, which values are allowed and how to fix it, so even a small model usually corrects itself.
Tell the agent that it manages your Appexbots shop and ask it to start with whoami — it gets the shop and bot identifiers right away. Good practice: ask the agent to search for a product before creating one (to avoid duplicates) and to confirm with you before deleting, sending mailings or changing prices.
Clients that support prompts get ready-made scenarios: import a catalog from a website, translate the catalog, weekly report, set up a new shop. For other clients the scenario texts are on the …/mcp/docs page.
The full list of tools with parameters and scopes: https://app.appexbots.com/app/mcp/docs (available in English, Russian and Thai). In short:
Intentionally not available to the agent: changing the bot token, managing managers, payment and delivery provider secrets, billing.