You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after updating claude studio for mac 1.26832.0 claude desktop can't use the server anymore. I get:
every Anki MCP tool call fails at the exact same validation step, complaining that the tool's declared output schema uses an old JSON Schema draft (draft-07) that this session's validator no longer accepts.
I haven't been able to reproduce this. I tested both 0.22.5 and 0.23.0 as MCPB extensions on Claude Desktop 1.28929.0: all 48 tools list correctly and calls return normally, including ones with large nested output schemas.
On the draft-07 part — worth clarifying, because it isn't something this server sets. The JSON Schema draft is emitted by the official MCP TypeScript SDK, which hardcodes draft-07 and exposes no option to change it (see modelcontextprotocol/typescript-sdk#745). I diffed the schema-generation code between SDK 1.29.0 and 1.30.0 and it is byte-for-byte identical, and this server has been on that same code path for many releases. So there's no recent change here that could have introduced it, and downgrading the server won't help.
Your Claude Desktop is 1.26832.0, which is older than the build I tested against. My best guess is a stricter validator in that specific version that has since been fixed.
Two things that would help narrow it down:
Could you update Claude Desktop and let me know whether it resolves?
Do your other MCP servers still work? Nearly all TypeScript-based MCP servers carry the same draft-07 schemas, so if those are failing too it points at the client rather than this server.
I've the same issue, but for latest Claude Desktop version 1.28929.0 (I use Code tab there)
Error: Tool 'listDecks' has an invalid outputSchema: JSON Schema declares an unsupported dialect ("$schema": "http://json-schema.org/draft-07/schema#"). The default validator supports JSON Schema 2020-12 only; pass a pre-configured Ajv instance to AjvJs
Update — @mazurov's error message cracked this open. Thanks for posting the verbatim text, that was the missing piece.
Correcting my earlier reply: this is not limited to older Claude Desktop builds, and it is reproducible on current ones. The trigger is the Code tab, which validates the declared schema dialect; the regular Desktop chat client does not, which is why my first round of testing passed on 1.28929.0.
Root cause is upstream, in the MCP TypeScript SDK. SEP-1613 made JSON Schema 2020-12 the default dialect for inputSchema/outputSchema, but the SDK still emits draft-07. On 1.30.0 (the latest release) there's no way to opt out: server/mcp.js calls the converter with a hardcoded options object and never passes a target, and there's no path to supply a pre-built 2020-12 schema instead. So nothing in this repo's configuration can change it.
Fixes are in flight upstream, both targeting the v1.x line:
Since neither has landed yet and this makes the server unusable in the Code tab, I'll ship a stopgap tomorrow that emits the schemas in the dialect the spec now expects. It'll be removed as soon as one of the upstream PRs is released.
Fixed. The change is on feat/mcp-nest-v2 (v0.24.0) and will be released shortly.
Rather than wait for either of the upstream 1.x PRs to land, the server now moves off the 1.x SDK entirely: @modelcontextprotocol/[email protected] is replaced by @modelcontextprotocol/{core,node,server} v2, which emits the dialect SEP-1613 requires. That also meant migrating @rekog/mcp-nest 1.9.11 → 2.0.0, since v2 of the SDK is what it peers on.
Verified against the built server — all 96 tool schemas (48 inputSchema + 48 outputSchema) now emit a single dialect:
No draft-07 anywhere on the wire. The MCPB bundle has been rebuilt and tested end-to-end in Claude Desktop's Code tab — the path that actually validates the dialect — and tool calls work. STDIO, HTTP and tunnel transports all verified.
@mazurov — thanks for posting the verbatim error text. Without the "unsupported dialect" wording this would still be filed as a client-version problem; it's what identified the Code tab as the trigger and pointed at SEP-1613.
Activity
anatoly314 commentedon Aug 12, 2026
Thanks for the report, and sorry for the hassle.
I haven't been able to reproduce this. I tested both 0.22.5 and 0.23.0 as MCPB extensions on Claude Desktop 1.28929.0: all 48 tools list correctly and calls return normally, including ones with large nested output schemas.
On the draft-07 part — worth clarifying, because it isn't something this server sets. The JSON Schema draft is emitted by the official MCP TypeScript SDK, which hardcodes draft-07 and exposes no option to change it (see modelcontextprotocol/typescript-sdk#745). I diffed the schema-generation code between SDK 1.29.0 and 1.30.0 and it is byte-for-byte identical, and this server has been on that same code path for many releases. So there's no recent change here that could have introduced it, and downgrading the server won't help.
Your Claude Desktop is 1.26832.0, which is older than the build I tested against. My best guess is a stricter validator in that specific version that has since been fixed.
Two things that would help narrow it down:
mazurov commentedon Aug 12, 2026
I've the same issue, but for latest Claude Desktop version 1.28929.0 (I use Code tab there)
anatoly314 commentedon Aug 12, 2026
Update — @mazurov's error message cracked this open. Thanks for posting the verbatim text, that was the missing piece.
Correcting my earlier reply: this is not limited to older Claude Desktop builds, and it is reproducible on current ones. The trigger is the Code tab, which validates the declared schema dialect; the regular Desktop chat client does not, which is why my first round of testing passed on 1.28929.0.
Root cause is upstream, in the MCP TypeScript SDK. SEP-1613 made JSON Schema 2020-12 the default dialect for
inputSchema/outputSchema, but the SDK still emits draft-07. On 1.30.0 (the latest release) there's no way to opt out:server/mcp.jscalls the converter with a hardcoded options object and never passes atarget, and there's no path to supply a pre-built 2020-12 schema instead. So nothing in this repo's configuration can change it.Fixes are in flight upstream, both targeting the v1.x line:
I've commented on both with this report.
Since neither has landed yet and this makes the server unusable in the Code tab, I'll ship a stopgap tomorrow that emits the schemas in the dialect the spec now expects. It'll be removed as soon as one of the upstream PRs is released.
Leaving this open until that's out.
anatoly314 commentedon Aug 13, 2026
Fixed. The change is on
feat/mcp-nest-v2(v0.24.0) and will be released shortly.Rather than wait for either of the upstream 1.x PRs to land, the server now moves off the 1.x SDK entirely:
@modelcontextprotocol/[email protected]is replaced by@modelcontextprotocol/{core,node,server}v2, which emits the dialect SEP-1613 requires. That also meant migrating@rekog/mcp-nest1.9.11 → 2.0.0, since v2 of the SDK is what it peers on.Verified against the built server — all 96 tool schemas (48
inputSchema+ 48outputSchema) now emit a single dialect:No draft-07 anywhere on the wire. The MCPB bundle has been rebuilt and tested end-to-end in Claude Desktop's Code tab — the path that actually validates the dialect — and tool calls work. STDIO, HTTP and tunnel transports all verified.
@mazurov — thanks for posting the verbatim error text. Without the "unsupported dialect" wording this would still be filed as a client-version problem; it's what identified the Code tab as the trigger and pointed at SEP-1613.
docs+test: changelog for v0.24.0, make three orphaned E2E specs reach…