Direct answer: test degraded operation, not only the happy path
A production acceptance test for Sanity MCP should verify what happens when schema context is incomplete, a deployed schema is parseable but rejected by the compiler, or the documentation backend times out. Sanity’s MCP server release v2.32.1, published on September 10, 2026, introduced four relevant fixes: get_schema can resolve the only deployed schema when workspaceName is absent and no default workspace exists; known document fields can be read without fetching a schema first; schema and document tools can read a deployed schema when its types remain parseable despite compiler rejection; and documentation timeouts reported by search_docs or read_docs are classified as temporary upstream issues worth retrying.
Those are confirmed product behaviors. They do not prove that every malformed schema is safe, that retries always succeed, or that an automated agent should continue without supervision. CreatikLab’s operational interpretation is narrower: use these behaviors to design explicit fallback tests, evidence requirements and stop conditions before allowing an AI workflow to read or act on production content.
