Log inSubmit server
Wix MCP logo

Wix MCP

Connects AI clients to Wix documentation, site APIs, site management, and account-level tools over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Wix MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-159": {
      "command": "npx",
      "args": [
        "-y",
        "arguments"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y arguments

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

Wix MCP MCP server connects AI clients with Wix documentation, Wix accounts, and selected site operations. It exposes tools for searching Wix SDK, REST, Design System, Build Apps, and Headless documentation, along with reading articles and API schemas. Use it when an agent needs Wix-specific implementation guidance or must query and act on Wix sites through the configured account.

Use cases

  • Search Wix SDK and REST documentation while implementing a feature
  • Read complete Wix API articles and method schemas
  • List Wix account sites before selecting a target
  • Call APIs or perform site-level actions on a Wix site

Key features

  • Searches Wix platform documentation
  • Reads full articles and API schemas
  • Lists sites for a Wix account
  • Calls APIs on selected Wix sites
  • Performs site-level actions
  • Provides multi-step business-flow guidance

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

21/22 checks healthy over the last 95d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · arguments (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars15Stargazers on the source repository.
npm downloads315Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.

How Wix MCP works

What Wix MCP MCP server does

Wix MCP MCP server gives an AI client access to Wix documentation and selected Wix account and site operations through the Model Context Protocol. It can search documentation for the Wix Design System, Wix REST APIs, Wix SDK, Wix Build Apps, and Wix Headless. It can also retrieve complete documentation articles and API method schemas.

For connected Wix accounts, the server can list available sites, call APIs for a selected site, and perform site-level actions such as creating a site. It also provides guided instructions for multi-step Wix business flows and a tool for sending user feedback to Wix.

How it works

The service is hosted remotely at https://mcp.wix.com/mcp and is added to an MCP-compatible client as an HTTP server. After configuration, the client can invoke the available tools as needed. All listed tools are enabled by default.

Documentation searches help an agent locate relevant Wix guidance before writing code or choosing an API. ReadFullDocsArticle retrieves an article when search results are not enough, while ReadFullDocsMethodSchema supplies the complete request and response schema for an API method. Site tools operate against an account and, where applicable, a selected site.

The repository also documents a command-line connection through @wix/mcp-remote, using the Wix server’s SSE endpoint. This can help isolate whether a client configuration is causing a connection problem.

Setup and configuration

Node.js 19.9.0 or newer is listed as a prerequisite. Add the remote server to the client’s MCP configuration with this structure:

config.json
{
  "mcpServers": {
    "wix-mcp-remote": {
      "type": "http",
      "url": "https://mcp.wix.com/mcp"
    }
  }
}

The exact configuration interface depends on the client. The documentation links setup instructions for Claude Desktop, Claude Web, Cursor, Windsurf, VS Code, and Gemini CLI.

If the connection fails, check IDE logs, confirm that the current Node installation is the expected version, verify the configuration arguments, and restart the client. The documented command-line check is npx -y @wix/mcp-remote https://mcp.wix.com/sse.

Tools and capabilities

Wix MCP MCP server includes these capabilities:

  • Search Wix Design System, REST, SDK, Build Apps, and Headless documentation.
  • Provide step-by-step instructions for multi-stage Wix business flows.
  • Read complete documentation articles by URL.
  • Return full request and response schemas for API methods.
  • List the sites associated with a Wix account.
  • Query or perform actions through a selected Wix site API.
  • Perform site-level operations, including site creation.
  • Collect and send user feedback to Wix.

Limitations and notes

The provided configuration describes a hosted HTTP endpoint rather than a locally implemented Wix service. Site actions and API calls are account- and site-dependent, so the relevant Wix account and target site must be available to the client.

Connections may be lost after extended inactivity or after changing the authenticated Wix account. Client logs and the MCP debugging guide are the recommended next places to investigate when restarting or reconfiguring the client does not resolve the issue.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Wix MCP

Wix MCP is an MCP server that connects an AI client to Wix documentation, Wix accounts, and selected Wix site operations. Its main tools search Wix documentation, read full articles and method schemas, list sites, call site APIs, manage sites, provide business-flow guidance, and send support feedback.

Add the hosted HTTP endpoint `https://mcp.wix.com/mcp` to your client’s MCP configuration. Node.js 19.9.0 or newer is required, and the README provides client-specific setup links for supported tools.

Yes, Wix MCP works with Cursor through its MCP server configuration. Add the remote HTTP URL `https://mcp.wix.com/mcp` and follow Cursor’s MCP setup instructions.

Wix MCP can list sites for a Wix account, call APIs for a selected site, and perform site-level actions such as creating a site. The available account and site determine which operations can be performed.

Check IDE logs, verify Node.js and the MCP configuration, restart the client, and test the documented `npx -y @wix/mcp-remote https://mcp.wix.com/sse` command. Removing the local `.mcp-auth` file may help after inactivity or an account switch.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWix MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-159?style=directory)](https://allmcps.com/mcp/mcp-159)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-159"><img src="https://allmcps.com/api/badge/mcp-159?style=directory" alt="Wix MCP on AllMCPs" /></a>