Read store products, orders, customers, categories and coupons; adjust inventory and update orders. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"ecwid": {
"url": "https://ecwid.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"ecwid": {
"type": "http",
"url": "https://ecwid.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Ecwid Store ID and Secret token.
Find both in the Ecwid Control Panel → Apps → Develop apps / My apps: the Store ID (a number) and the app's secret token (looks like secret_xxxxx). Your credentials are used only to call the API on your behalf and to derive a private store id; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Ecwid Store ID and Secret token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Ecwid connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
ecwid_get_store_profile | read | Get store profile Get the store's profile — general info (store id, name, currency), company details, and settings. Ecwid REST: GET /profile. |
ecwid_search_products | read | Search products Search / list the store's products with optional filters (keyword, SKU, category, stock, price range) and sorting. Returns a paged collection ({total, count, offset, limit, items}). Ecwid REST: GET /products. |
ecwid_get_product | read | Get product Get a single product by its id, including price, stock, options, images, and category assignments. Ecwid REST: GET /products/{productId}. |
ecwid_search_orders | read | Search orders Search / list the store's orders with optional filters (keyword, customer email/id, payment & fulfillment status, coupon, created-date range). Returns a paged collection. Ecwid REST: GET /orders. |
ecwid_get_order | read | Get order Get a single order by its order number, including line items, totals, customer, and payment/fulfillment status. Ecwid REST: GET /orders/{orderNumber}. |
ecwid_search_customers | read | Search customers Search / list the store's customers with optional filters (keyword, email, name, customer group). Returns a paged collection. Ecwid REST: GET /customers. |
ecwid_get_customer | read | Get customer Get a single customer by id, including contact details, addresses, and customer group. Ecwid REST: GET /customers/{customerId}. |
ecwid_list_categories | read | List categories List the store's product categories, optionally scoped to a parent category and including hidden ones. Returns a paged collection. Ecwid REST: GET /categories. |
ecwid_get_category | read | Get category Get a single category by id, including its name, parent, product ids, and images. Ecwid REST: GET /categories/{categoryId}. |
ecwid_list_discount_coupons | read | List discount coupons List the store's discount coupons with optional filters (coupon code, discount type, availability). Returns a paged collection. Ecwid REST: GET /discount_coupons. |
ecwid_adjust_product_inventory | write | Adjust product inventory ADJUSTS a product's in-stock quantity by a delta — this MODIFIES live store data. Positive increases stock, negative decreases it. Ecwid REST: PUT /products/{productId}/inventory with JSON body {quantityDelta}. Returns {updateCount, warning?}. |
ecwid_update_order | write | Update order UPDATES an order — its payment status, fulfillment status, and/or tracking number. This MODIFIES live store data and may trigger customer notifications. Ecwid REST: PUT /orders/{orderNumber}. Provide only the fields you want to change. Returns {updateCount}. |
ecwid_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
ecwid_request_feature | Request a missing feature Tell usefulapi that the user needs something the Ecwid tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
ecwid_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Ecwid tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
ecwid_cancel_subscription | Cancel the Pro subscription Cancel the caller's Ecwid Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run ecwid_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Ecwid server only. Subscribe with ecwid_upgrade (it returns a Stripe Checkout link). Cancel any time with ecwid_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running ecwid_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Ecwid. The server calls the Ecwid API with your own Ecwid access, so it sees only the data that your account can see.
The login page asks for your Ecwid Store ID and Secret token. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Ecwid Store ID and Secret token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Ecwid API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Ecwid.
Yes, if you approve it. 2 of the 12 Ecwid tools can create or change data. The other 10 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Ecwid server only. Run ecwid_usage_status to see how many calls you used.
Ask the AI to run ecwid_upgrade: it returns a Stripe Checkout link. To cancel, run ecwid_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with ecwid_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.