Wix MCP server
Wix in any MCP client, through Memtro: Wix does not publish this server. Memtro's Wix connector reads Wix through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Wix site data: the site's contacts (name, email, company), eCommerce orders with status, totals and items, and Wix Bookings appointments with service, time and status. Can add, edit, label and delete a contact, confirm, decline or cancel a booking, cancel or archive an order, and mark order items as shipped.
Reads
wix_list_contactsContacts on the Wix site, newest first: name, primary email, company and job title.wix_list_ordersECommerce orders on the Wix site, newest first: number, status, payment and fulfilment status, total and currency, items, and the buyer's name.wix_list_bookingsWix Bookings appointments and class bookings, soonest first: service, start and end (UTC), status, payment status…wix_list_labelsContact labels on the Wix site (key and display name), to find the label keys wix_label_contact needs.
Acts, when you ask
These change something in Wix. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
wix_create_contactAdds one contact to the Wix site's contact list (Contacts in the site dashboard), as the API key.wix_update_contactEdits one contact on the Wix site: first name, last name, company or job title.wix_label_contactAdds labels to one Wix contact, by label key (find keys with wix_list_labels).wix_unlabel_contactRemoves labels from one Wix contact, by label key.wix_delete_contactPermanently deletes one contact from the Wix site's contact list.wix_confirm_bookingConfirms one PENDING, CREATED or WAITING_LIST Wix booking, without re-checking that the slot is still free.wix_decline_bookingDeclines one PENDING, CREATED or WAITING_LIST Wix booking; it cannot be confirmed afterwards.wix_cancel_bookingCancels one Wix booking: the appointment leaves the calendar, or the customer leaves the class or course, and the slot is released.wix_cancel_orderCancels one Wix eCommerce order (status becomes CANCELED).wix_archive_orderArchives one Wix order (hides it from the dashboard's main orders view; it stays retrievable) or, with archived false, unarchives it.wix_create_fulfillmentMarks line items of one APPROVED Wix order as shipped, with optional tracking.
Connect it
First connect Wix on Dashboard → Connections, then add Memtro to your client once. The Wix tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Wix connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What orders came in on our Wix store this week?
- › Which Wix orders are still unpaid?
- › Who is booked in for tomorrow?
- › Add Dan Fletcher from Northwind as a contact on our Wix site.
- › Mark order 10452 as shipped with tracking number RX4471
Questions
- Is this an official Wix MCP server?
- No. It is Memtro's MCP server with Memtro's Wix connector behind it: the connector reads Wix through its API with the credentials you connect on Dashboard → Connections, and Wix publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Wix?
- Only when you ask, and only what it has been granted: add a contact to the site's contact list; edit a contact's name, company or job title; add labels to a contact or remove them; permanently delete a contact; confirm or decline a pending booking; cancel a booking; cancel an eCommerce order; archive or unarchive an order; mark order items as shipped, with tracking. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.