Wix MCP connector for AI agents

Wix MCP tools for AI agents

CALL ANY TOOL

12 tools covering create, get, list.

wixmcp_wixreadme

Wixreadme

Read the Wix MCP README for guidance on how to use the available Wix tools effectively.

Parameters

Name

Type

Required

Description

—

No parameters required

wixmcp_listwixsites

Listwixsites

wixmcp_executewixapi

Executewixapi

Execute JavaScript code against the Wix REST API in a sandboxed environment to query or mutate site data.

Parameters

Name

Type

Required

Description

code

string

Required

JavaScript async function expression to execute against the Wix REST API. The value must be the function itself, for example `async function() { ... }` or `async () => { ... }`, not a script body and not an invoked function. Return the final answer from inside the function. Do not write top-level `const`, top-level `await`, or top-level `return` outside the function body. Use `wix.request({ method, url, body })` for Wix API calls. Scope defaults to `site` when the ExecuteWixAPI `siteId` parameter is passed, otherwise `account`; set `scope` explicitly when needed. Full Wix API URLs and paths starting with `/` are supported. Do not pass `siteId` inside `wix.request()`; one ExecuteWixAPI call can target only the tool-level `siteId`.

hasMutations

boolean

Required

Whether this code creates, updates, deletes, publishes, installs, imports, uploads, or otherwise mutates Wix data or site/account state. Set this to true for create/update/delete/bulk create/import/upload calls even if the reason is inspection, verification, or response-shape discovery. Read-only GET/query/list/search calls can use false.

reason

string

Required

One sentence explaining the original user request and why you are executing code to complete it.

sourceDocUrls

array

Required

The URLs of the documentation, recipes, API articles, or schema sources where you confirmed the Wix REST endpoints, HTTP methods, request body shapes, auth contexts, and required fields used by this code. Include every docs/schema source needed for the endpoints and request shapes used in the code. MAKE SURE THE ENDPOINT URLS AND REQUEST SHAPES ARE REALLY THERE AND YOU ARE NOT GUESSING THEM !!! Each value must be a valid URL like: - https://dev.wix.com/docs/api-reference/... (REST API reference docs) Use ["user-provided"] if the user gave you all endpoint and request details directly. Use ["other"] ONLY IF YOU HAVE A VERY GOOD REASON TO DO SO

siteId

string

Optional

Wix site ID for site-level API calls. Required when using `wix.request({ scope: "site", ... })`. One ExecuteWixAPI call can target only this siteId; per-request siteId inside `wix.request()` is not supported. Find site IDs using ListWixSites or an account-level `wix.request()` call to query the Sites API.

wixmcp_managewixsite

Managewixsite

wixmcp_callwixsiteapi

Callwixsiteapi

Call any Wix REST API endpoint on a specific site to create, read, update, or delete site data.

Parameters

Name

Type

Required

Description

method

string

Required

The HTTP method to use for the API call (e.g. GET, POST, PUT, DELETE)

reason

string

Required

One sentence explaining the original user request and why you are calling this API to complete it.

siteId

string

Required

The id of the site selected using site selection tool

sourceDocUrl

string

Required

The URL of the documentation or recipe where you found this API endpoint. MAKE SURE THE ENDPOINT URL IS REALLY THERE AND YOUR ARE NOT GUESSING IT !!! Must be a valid URL like: - https://dev.wix.com/docs/api-reference/... (REST API reference docs) Use "user-provided" if the user gave you the endpoint directly. Use "other" ONLY IF YOU HAVE A VERY GOOD REASON TO DO SO

url

string

Required

The url of the api to call - ALWAYS get the API url from the Wix REST docs or from the conversation context, the URL MUST BE ABSOLUTE URL NEVER guess the API url, ALWAYS get it from the conversation context, i.e from the user prompt or from the "WixREADME" tool or from the "SearchWixRESTDocumentation" tool or from the "BrowseWixRESTDocsMenu" tool or from the "ReadFullDocsArticle" tool Allowed API urls are: wix.com, dev.wix.com, manage.wix.com, editor.wix.com, wixapis.com Docs urls like https://dev.wix.com/docs/... are not API urls, if you want to read the docs, use the "ReadFullDocsArticle" tool

body

string

Optional

The request body as a JSON object or array with all the required fields and values, including nested objects. Pass the actual value (object or array), NOT a JSON string. YOU MUST NEVER MAKE UP A BODY - the body should be based on the conversation context, i.e from the user prompt OR got into the conversation context by the "ReadFullDocsArticle" tool OR by the "SearchWixAPISpec" tool OR by the "ReadFullDocsMethodSchema" tool - i.e based on the API docs, a relevant recipe you read (preferably), a code example you found in the docs, a schema you read etc.. YOU MUST NEVER ASSUME YOU KNOW WHAT THE BODY SCHEMA IS WITHOUT CONCRETE EXAMPLES OR SCHEMA DEFINITIONS FROM THE CONVERSATION CONTEXT. Prefer reading relevant recipes if you have them in context for understand the body schema for API calls.

wixmcp_getsitecontext

Getsitecontext

wixmcp_wixsitebuilder

Wixsitebuilder

wixmcp_searchwixapispec

Searchwixapispec

wixmcp_claimanonymoussite

Claimanonymoussite

wixmcp_supportandfeedback

Supportandfeedback

wixmcp_getsuggesteddomains

Getsuggesteddomains

wixmcp_pullsitecreationjob

Pullsitecreationjob

wixmcp_readfulldocsarticle

Readfulldocsarticle

wixmcp_searchsitetemplates

Searchsitetemplates

wixmcp_uploadimagetowixsite

Uploadimagetowixsite

wixmcp_browsewixrestdocsmenu

Browsewixrestdocsmenu

wixmcp_createsitefromtemplate

Createsitefromtemplate

wixmcp_createwixbusinessguide

Createwixbusinessguide

wixmcp_readfulldocsmethodschema

Readfulldocsmethodschema

wixmcp_searchwixclidocumentation

Searchwixclidocumentation

wixmcp_searchwixsdkdocumentation

Searchwixsdkdocumentation

wixmcp_searchwixwdsdocumentation

Searchwixwdsdocumentation

wixmcp_searchwixrestdocumentation

Searchwixrestdocumentation

wixmcp_searchbuildappsdocumentation

Searchbuildappsdocumentation

wixmcp_searchwixheadlessdocumentation

Searchwixheadlessdocumentation

wixmcp_import_claude_design_from_url

Import claude design from url

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="wixmcp")

mcp = MultiServerMCPClient({
    "wixmcp": {
        "url": "https://mcp.scalekit.com/wixmcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "wixmcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/wixmcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "wixmcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/wixmcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="wixmcp")
# Connect to MCP at https://mcp.scalekit.com/wixmcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Copy the prompt

Copied

Create or build a new Wix site using AI, returning a job ID to track the creation progress?

Copy the prompt

Copied

Read the Wix MCP README for guidance on how to use the available Wix tools effectively?

Advanced

Copy the prompt

Copied

Upload one or more images to a Wix site’s Media Manager and return the file URL and media ID?

Copy the prompt

Copied

Submit feedback or a support request about the Wix MCP tools to the Wix team?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Wix MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Wix MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Wix MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Wix MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering Teams

Auto release notes agent

Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Wix as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Wix OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Wix?
Yes. Pass a tool name filter to listScopedTools so the DevOps agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Wix.

What happens when a user revokes Wix access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent call any Wix REST API on my site?
Only APIs the authorizing user's Wix account can reach. Site API calls and media uploads run under that user's permissions, and you can filter tools to keep the agent read-only on production sites.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit