Direct answer: what changed and what still needs testing
Sanity MCP server v2.32.1 contains four relevant fixes. The get_schema tool can resolve the only deployed schema when no workspace name is supplied and no default workspace exists. Reads of known document fields can proceed without first fetching a schema. The search_docs and read_docs tools now classify documentation-backend timeouts as temporary upstream problems worth retrying rather than internal errors. Schema and document tools can also read a deployed schema when its types are parseable even if the schema compiler rejects it. These are confirmed product changes, not proof that a particular implementation is production-ready.
CreatikLab’s operational conclusion is therefore conditional: update the test environment, reproduce the previously fragile paths, and accept the integration only when evidence shows that schema selection, field access and retry behavior match the intended workflow. Sanity does not state that every schema issue is repaired, that retries happen automatically, or that business content is protected from incorrect agent actions.
