Wix MCP Server
Connect AI agents to Wix's developer platform — search docs, write Wix code, and call site APIs.
Updated
What is Wix MCP?
The Wix MCP server is a Model Context Protocol server that connects AI tools to Wix's developer platform, giving them live access to Wix documentation, APIs, and site-management functionality. It is officially built and hosted by Wix.
With it connected, an AI client can search the Wix documentation, write code for the Wix platform (Velo, the Wix SDK, REST APIs, and headless), and make authenticated API calls against your Wix sites — instead of you copying snippets from docs by hand. It exposes documentation-search and doc-reading tools alongside site tools for listing sites and calling their APIs.
The remote server is reachable at https://mcp.wix.com/sse (an HTTP/https://mcp.wix.com/mcp endpoint is also available in newer configs). Documentation search works unauthenticated, while reading and acting on your sites uses an OAuth-style sign-in flow that stores credentials in a local auth file. A self-hosted option is also published as the @wix/mcp-remote npm package for clients that need a stdio bridge.
Tools the Wix MCP server exposes
| Tool | What it does |
|---|---|
| SearchWixWDSDocumentation | Search the Wix Design System (WDS) documentation. |
| SearchWixRESTDocumentation | Search the Wix REST API documentation. |
| SearchWixSDKDocumentation | Search the Wix SDK documentation. |
| SearchBuildAppsDocumentation | Search documentation for building Wix apps. |
| SearchWixHeadlessDocumentation | Search the Wix headless documentation. |
| WixBusinessFlowsDocumentation | Look up documentation for Wix business flows. |
| ReadFullDocsArticle | Read the full contents of a Wix documentation article. |
| ReadFullDocsMethodSchema | Read the full schema for a Wix API method. |
| ListWixSites | List the Wix sites available to the authenticated account. |
| CallWixSiteAPI | Make an API call against a specific Wix site. |
| ManageWixSite | Perform management actions on a Wix site. |
| SupportAndFeedback | Submit support requests and feedback to Wix. |
Connect the Wix MCP server
Claude Code
- 1
Add the remote server
Run: claude mcp add --transport sse wix https://mcp.wix.com/sse
- 2
Authenticate
On first use of a site tool, Claude Code triggers the Wix OAuth sign-in in your browser; approve access. Credentials are cached locally.
- 3
Verify
Run /mcp in Claude Code and confirm the wix server is connected, then ask it to list your Wix sites.
Cursor
- 1
Open MCP settings
Go to Cursor Settings -> MCP -> Add new MCP server (or edit ~/.cursor/mcp.json).
- 2
Add the Wix server
Add an entry with command npx and args ["-y", "@wix/mcp-remote", "https://mcp.wix.com/sse"], or configure the remote URL https://mcp.wix.com/sse directly if your version supports remote servers.
- 3
Authenticate and use
Reload Cursor; complete the Wix OAuth prompt in your browser when prompted, then the Wix tools appear in the agent.
Sample use cases
An engineer building on Wix wants accurate, current API and SDK details inside their editor.
The agent searches Wix REST/SDK/headless docs and reads full method schemas, then writes correct Velo/SDK code without manual doc hunting.
A team needs to query or update content and commerce data across their Wix sites programmatically.
The agent lists sites, calls the relevant site APIs, and applies managed changes through the MCP tools.
Security & permissions
Documentation-search tools work without authentication. Acting on your sites (listing sites, calling site APIs, managing sites) requires signing in to your Wix account through an OAuth-style flow; the resulting credentials are stored in a local auth file (~/.mcp-auth on macOS/Linux). The connected agent operates with the permissions of the authenticated Wix account, so it can read and modify the sites that account can access — grant access only to trusted clients and review actions on production sites.
Using Wix MCP with Gamut
In a Gamut workflow, the Wix MCP server runs as a connected tool that an agent calls on a schedule or in response to events — Gamut manages the OAuth connection and credentials. For example, a scheduled agent could query a Wix site's content or commerce data via CallWixSiteAPI, look up the correct API shape using the documentation-search and schema tools, and apply updates through ManageWixSite, then hand results off to downstream steps (notifications, reports). Gamut handles connection and triggering; the agent stays within the permissions of the authenticated Wix account.
Frequently asked questions
What is the Wix MCP server?
It is an officially hosted Model Context Protocol server from Wix that connects AI tools to the Wix developer platform, letting an agent search Wix documentation, write Wix code, and make API calls against your Wix sites. It's reachable at https://mcp.wix.com/sse.
Is the Wix MCP server free?
Wix does not document a separate fee for the MCP server — it's offered as part of the Wix developer platform, with standard Wix account and plan terms applying. Documentation search works without authentication; site actions require signing in to your Wix account.
How do I connect the Wix MCP server to Claude or Cursor?
Point your client at the remote server https://mcp.wix.com/sse (in Claude Code: claude mcp add --transport sse wix https://mcp.wix.com/sse; in Cursor: add it via MCP settings or run npx -y @wix/mcp-remote https://mcp.wix.com/sse). Complete the Wix OAuth sign-in in your browser when first using a site tool.
Is the Wix MCP server hosted or self-hosted?
Both. Wix officially hosts the remote server at https://mcp.wix.com/sse (with an HTTP endpoint also available), and a self-hosted stdio bridge is published as the @wix/mcp-remote npm package for clients that don't support remote MCP servers.