AI Apps (MCP) · Adyvance Developers

Server address

https://mcp.adyvance.com/mcp

The same address is shown in the admin under Apps → Developer → MCP server. AI apps are part of the Startup and Business plans.

Two ways to connect

Way	For	How it works
Sign in with Adyvance	Claude.ai, ChatGPT and other apps that sign in	The app sends you to Adyvance. You sign in, see what the app asks for, choose the store and permissions, and approve.
API key	Claude Code, Cursor, VS Code, Claude Desktop	Make a key in the admin with the permissions the app should have, and paste it into the app's settings.

Either way the app gets only the permissions you gave, never more than you have yourself. Connected apps are listed under Connected AI apps on the MCP server page, where you can disconnect one at any time.

Claude.ai

In Claude, open Settings → Connectors → Add custom connector.
Paste the server address and choose Add.
Choose Connect, sign in to Adyvance and approve.

ChatGPT

In ChatGPT, open Settings → Apps & Connectors → Advanced, and turn on developer mode.
Create a connector with the server address and OAuth sign-in.
Sign in to Adyvance and approve.

Claude Code

Run this in a terminal, with your key in place of YOUR_API_KEY:

claude mcp add --transport http adyvance https://mcp.adyvance.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "adyvance": {
      "url": "https://mcp.adyvance.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

VS Code

.vscode/mcp.json

{
  "servers": {
    "adyvance": {
      "type": "http",
      "url": "https://mcp.adyvance.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Desktop

Claude Desktop starts local servers only, so it connects through a small bridge that runs with npx. It needs Node.js.

claude_desktop_config.json

{
  "mcpServers": {
    "adyvance": {
      "command": "npx",
      "args": [
        "-y",
        "github:adyvanceofficial/adyvance-mcp"
      ],
      "env": {
        "ADYVANCE_MCP_URL": "https://mcp.adyvance.com/mcp",
        "ADYVANCE_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

The bridge's source and its own guide are on GitHub.

Config files hold your key

Do not commit .cursor/mcp.json, .vscode/mcp.json or other files with a key in them. Give each app its own key, so you can revoke one without touching the rest.

What AI apps can do

Each tool needs its permission. Tools that look things up answer at once. Tools that change something first show a preview of the change; it runs only after the person agrees, so an AI app never changes a shop on its own.

Tool	Does	Needs	Kind
`list_stores`	List your stores	Any key	Looks up
`search_orders`	Find orders	`orders.read`	Looks up
`get_order`	Open an order	`orders.read`	Looks up
`search_products`	Find products	`products.read`	Looks up
`get_product`	Open a product	`products.read`	Looks up
`list_categories`	List categories	`products.read`	Looks up
`search_customers`	Find customers	`customers.read`	Looks up
`get_customer`	Open a customer	`customers.read`	Looks up
`check_stock`	Check stock	`inventory.read`	Looks up
`update_order_status`	Change an order's status	`orders.update`	Changes, after a yes
`update_order_details`	Edit an order's note or tags	`orders.update`	Changes, after a yes
`create_product`	Create a product	`products.write`	Changes, after a yes
`update_product`	Edit a product	`products.write`	Changes, after a yes
`update_variant`	Change a price or SKU	`products.write`	Changes, after a yes
`adjust_stock`	Adjust stock	`inventory.adjust`	Changes, after a yes

AI apps use the same rate limits as the REST API, and everything they change is recorded in the shop's activity log like any other change.