CodeStringers MCP Server

 ⟨347 unchanged words⟩ `scope`, `siteId`, Authorization, wix-site-id, or wix-account-id.

File and export limits: ExecuteWixAPI is only for Wix REST API calls and in-memory data shaping. It does not provide Node.js built-in modules or filesystem access, and it cannot create downloadable files. Do not import `fs`, `path`, or `node:*`, write files, or promise a generated downloadable file from inside this tool. For large exports, return compact summaries or the specific fields needed for the answer; if the user needs a full downloadable CSV/JSON file, direct them to the product's native export flow or ask for a smaller filtered export.

Probing should be read-only: use GET/query/list/search to inspect ⟨171 unchanged words⟩  item to just the fields the task needs. When the code CREATES entities (create, bulk create, import, duplicate, upload), ALWAYS include the ID of every created entity in the returned object — e.g. `{ cartId }` or `{ createdIds: [...] }` — even if the user did not ask for them; follow-up steps, verification, and cleanup all need those IDs, and recovering them later costs extra query calls.

Example — a multi-step recipe (resolve a  ⟨93 unchanged words⟩ 

 ⟨61 unchanged words⟩ , or top-level `return` outside the function body. Do not import Node.js built-ins such as `fs`, `path`, or `node:*`, and do not try to write files from this code; ExecuteWixAPI only returns data from the function. Use `wix.request({ method, url, body }) ⟨320 unchanged words⟩ 

 ⟨26 unchanged words⟩ either be general docs articles or method articles.
Take the URL from the user's message or an earlier tool result. To reach an article you have no URL for, search or browse the docs first.
For REST docs, use the URL as-is. For ⟨103 unchanged words⟩  Wix APIs until the task is completed.
**Exception — creating a new Wix site/website:** IfFor thea usernormal askscreation torequest create,— buildand only then — skip WixREADME and the docs search, orand generateroute astraight newto the Wix site/website,site-creation skiptools available to you; their descriptions carry the routing rules. Everything else starts with WixREADME and:
-as usual.
If the user **explicitly**explicitly mentionsasks for a templateheadless site, Wix StudioClassic Editor site, or headlessmanual →account/API-based site creation, call CreateWixBusinessGuide directly.right away — these don't need the site's purpose first.
Never default to AI or search templates unless the user explicitly requests it. When the user named no creation method - Otherwiselet →the calluser make that choice as the WixSiteBuildersite-creation tooltools' directly.descriptions direct. Never route normal site creation through ManageWixSite, CallWixSiteAPI, or ExecuteWixAPI.
**Exception:** If the user asks to list ⟨72 unchanged words⟩  the WixREADME tool until the task is completed.
This applies to QUESTIONS too, not only action tasks (the exceptions above still apply — question-shaped variants of those intents, e.g. "can you show my sites?", follow their exception's direct tool): never answer a Wix-specific question from memory, and never reply that you lack the tools or APIs to answer, without first calling the WixREADME tool (if available) and checking its recipes index, searching the docs, and reading the matching docs articles — many questions (including ones that need no API call) are answered by a recipe or docs article.
If the user prompt / task is an ⟨323 unchanged words⟩ 

 ⟨187 unchanged words⟩  Wix APIs until the task is completed.
**Exception — creating a new Wix site/website:** IfFor thea usernormal askscreation torequest create,— buildand only then — skip WixREADME and the docs search, orand generateroute astraight newto the Wix site/website,site-creation skiptools available to you; their descriptions carry the routing rules. Everything else starts with WixREADME and:
-as usual.
If the user **explicitly**explicitly mentionsasks for a templateheadless site, Wix StudioClassic Editor site, or headlessmanual →account/API-based site creation, call CreateWixBusinessGuide directly.right away — these don't need the site's purpose first.
Never default to AI or search templates unless the user explicitly requests it. When the user named no creation method - Otherwiselet →the calluser make that choice as the WixSiteBuildersite-creation tooltools' directly.descriptions direct. Never route normal site creation through ManageWixSite, CallWixSiteAPI, or ExecuteWixAPI.
**Exception:** If the user asks to list ⟨72 unchanged words⟩  the WixREADME tool until the task is completed.
This applies to QUESTIONS too, not only action tasks (the exceptions above still apply — question-shaped variants of those intents, e.g. "can you show my sites?", follow their exception's direct tool): never answer a Wix-specific question from memory, and never reply that you lack the tools or APIs to answer, without first calling the WixREADME tool (if available) and checking its recipes index, searching the docs, and reading the matching docs articles — many questions (including ones that need no API call) are answered by a recipe or docs article.
If the user prompt / task is an ⟨323 unchanged words⟩