CodeStringers MCP Server

{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['reason'], 'properties': {'reason': {'type': 'string', 'description': 'One sentence describing the original user request and why you are browsing this part of the docs menu.'}, 'menuUrl': {'type': 'string', 'description': 'URL of the menu to browse. Empty/omitted returns the root menu. Copy the URL from links in previous responses of this tool. Example: "https://dev.wix.com/docs/api-reference/ecommerce" or "https://dev.wix.com/docs/api-reference/ecommerce/catalog"'}}, 'additionalProperties': False}

{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['visitorToken', 'url', 'method'], 'properties': {'url': {'type': 'string', 'format': 'uri', 'description': "The url of the api to call - ALWAYS get the information from the API docs retrieved using the 'SearchSiteApiDocs' tool or from the conversation context, the URL MUST BE ABSOLUTE URL. Usually it starts with 'https://www.wixapis.com'."}, 'body': {'type': 'string', 'description': 'A string representing of a valid JSON object to describe the body of the request'}, 'method': {'type': 'string', 'description': 'The HTTP method to use for the API call (e.g. GET, POST, PUT, DELETE)'}, 'visitorToken': {'type': 'string', 'description': 'Visitor access token. If you have it in your context, ALWAYS use it and not create a new one. If you do not have it in your context, use the GenerateVisitorToken tool to get it.'}}, 'additionalProperties': False}

{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['code', 'reason', 'hasMutations', 'sourceDocUrls', 'visitorToken'], 'properties': {'code': {'type': 'string', 'description': '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. Every call runs against the current visitor site; do not set `scope`, `siteId`, or auth headers. Full Wix API URLs and paths starting with `/` are supported. Wix REST API page size limits vary — use 100 as a safe default unless the method schema (via SearchWixAPISpec) confirms a higher limit is supported. For cursor-based APIs, pass the next cursor as `cursorPaging: { limit: 100, cursor: pagingMetadata.cursors.next }` — not inside `paging`. Check the method schema to confirm whether the API uses `paging` (offset-based) or `cursorPaging` (cursor-based) before paginating.'}, 'reason': {'type': 'string', 'description': 'One sentence explaining the original user request and why you are executing code to complete it.'}, 'hasMutations': {'type': 'boolean', 'description': 'Whether this code creates, updates, deletes, publishes, imports, uploads, or otherwise mutates site data on the visitor’s behalf. 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.'}, 'visitorToken': {'type': 'string', 'description': 'Visitor access token. If you have it in your context, ALWAYS use it and do not create a new one. If you do not have it in your context, use the GenerateVisitorToken tool to get it.'}, 'sourceDocUrls': {'type': 'array', 'items': {'type': 'string'}, 'description': '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.\nInclude every docs/schema source needed for the endpoints and request shapes used in the code.\nMAKE SURE THE ENDPOINT URLS AND REQUEST SHAPES ARE REALLY THERE AND YOU ARE NOT GUESSING THEM !!!\nEach value must be a valid URL like:\n- https://dev.wix.com/docs/api-reference/... (REST API reference docs)\nUse ["user-provided"] if the user gave you all endpoint and request details directly.\nUse ["other"] ONLY IF YOU HAVE A VERY GOOD REASON TO DO SO'}}, 'additionalProperties': False}

{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}

{'type': 'object', 'properties': {}}

{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['articleUrl'], 'properties': {'articleUrl': {'type': 'string', 'format': 'uri', 'description': 'The URL of the docs article or method article to fetch. Should be something like https://dev.wix.com/docs/.../... For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include the query param ?apiView=SDK (e.g. https://dev.wix.com/docs/...?apiView=SDK).'}}, 'additionalProperties': False}

{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['articleUrl', 'reason'], 'properties': {'reason': {'type': 'string', 'description': 'One sentence describing the original user request, the task you are trying to accomplish, and why you need the full schema (e.g., no relevant code example found in docs or recipes).'}, 'articleUrl': {'type': 'string', 'format': 'uri', 'description': 'The URL of the documentation to fetch. Should be something like https://dev.wix.com/docs/.../... For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include the query param ?apiView=SDK (e.g. https://dev.wix.com/docs/...?apiView=SDK).'}}, 'additionalProperties': False}

{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['searchTerm'], 'properties': {'searchTerm': {'type': 'string', 'description': 'The term to search for in the site, e.g. "working hours" or "store locations"'}}, 'additionalProperties': False}

{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['searchTerm'], 'properties': {'searchTerm': {'type': 'string', 'description': 'A short, natural-language search term describing the API capability you need — a generic term, not too specific (e.g., "how to fetch products" instead of "avocados in stock"). Use plain words only: no code, SQL, shell commands, HTML, URLs, file paths, or special symbols.'}}, 'additionalProperties': False}