WixREADMELABSCO SUMMARY
Having the schema and the call in one connection is what stops the guess-and-fail loop.
The usual failure when an agent writes against a platform API is inventing a field name that sounds right. Being able to fetch the actual schema, then make the call, in the same conversation, removes the guess entirely — and when it does fail you can re-read the schema rather than retrying with a different invention. That pairing is more valuable than either half alone, and it is why documentation endpoints that cannot act are only half a tool.
What it is
Wix's endpoint is two things at once: a documentation surface for people building on Wix, and a live one for acting on the sites in your account.
What you get
- Searching their REST, SDK, design system, app-building and headless documentation
- Reading a full article, or an API schema
- Listing the sites in your account
- Calling a site's API, and site-level management operations
Requirements
OAuth sign-in for interactive use; an API key with an account-id header for automation platforms. Clients without remote support use their published proxy.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
Building on Wix
Search the docs and read the API schema before writing code.
Acting on a site
List your sites, then call that site's API.
Automating from a platform
API key with an account-id header instead of an interactive sign-in.
18 tools
Listed in project docs. Your client may show a different list.
SearchWixWDSDocumentationSearchWixRESTDocumentationSearchWixSDKDocumentationSearchBuildAppsDocumentationSearchWixHeadlessDocumentationWixBusinessFlowsDocumentationBrowseWixRESTDocsMenuReadFullDocsArticleReadFullDocsMethodSchemaSearchWixAPISpecListWixSitesGetSiteContextCallWixSiteAPIExecuteWixAPIManageWixSiteUploadImageToWixSiteSupportAndFeedbackBEFORE YOU INSTALL
What to know first
Tools you get
18 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth sign-in by default, or an API key with an account-id header for programmatic use
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
https://mcp.wix.com/mcpRequirements
- OAuth sign-in by default, or an API key with an account-id header for programmatic use