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
{{ message }}
Repository navigation
Commit 8aa3cb1
Browse filesBrowse the repository at this point in the historyBrowse files
Remove outputSchema: Claude Desktop rejects the draft-07 dialect the SDK emits
@modelcontextprotocol/sdk (server-side, currently 1.30.0) generates
outputSchema via zod-to-json-schema, which stamps "$schema": draft-07 on
every schema. Claude Desktop's bundled MCP client validates declared
schemas against 2020-12 only and rejects draft-07 outright, so every
tool call failed with "invalid outputSchema ... unsupported dialect".
This is a known interop gap between v1-SDK servers and v2 clients
(modelcontextprotocol/typescript-sdk#2532, anthropics/claude-code#86142).
The fix landed in a separate client package this server doesn't control,
so outputSchema is dropped from all 22 tools until Claude Desktop ships
an updated bundled client. The Zod schemas stay in api/types.ts as the
source of truth, ready to be re-wired once the client-side fix rolls out.
api/types.ts is now excluded from coverage: every consumer imports it
with `import type`, which tsc erases entirely, so the module is never
loaded at runtime (0 executable lines, not merely untested).
Co-Authored-By: Claude Sonnet 5 <[email protected]>
0 commit comments