Move MCP templates to the v2 SDKs

[Larry-Osakwe]

Final PR of the MCP v2 cutover. keycardai-mcp 2.0.0 and @keycardai/mcp 2.0.0 are published, so the five templates on the v1 line move over. Go templates are untouched (no Go v2; they got v1.7.0 in #19).

Python — 2 templates

• keycardai-mcp>=2,<3, interim mcp<2.0 pins from Bump MCP dependencies across templates #19 removed
• mcp.server.fastmcp → mcp.server.mcpserver; streamable_http_path moved from the constructor to streamable_http_app()
• Both resolve keycardai-mcp 2.0.0 + mcp 2.0.0 and import clean

TypeScript — 3 templates

• @keycardai/mcp ^2.0.0; v1 @modelcontextprotocol/sdk replaced by the v2 split: /server + /node for servers, /client for clients (Client, StreamableHTTPClientTransport, and the PRM discovery helpers all export from its root)
• server.tool(name, desc, shape, cb) → registerTool(name, {description, inputSchema}, cb)
• Tool handlers read auth from ctx.http.authInfo (was extra.authInfo)
• zod ^4: v2 types its schema overloads against zod 4, and z.record now requires an explicit key type
• All three typecheck and build

The brokered TS template and snowflake-wif exercise the v2 client path (including PRM discovery), which the server templates don't — so this PR's CI run is also the first live test of that half against published packages.

CI verifies every changed template against a real ephemeral zone.

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​modelcontextprotocol/​node@​2.0.0
	npm/​snowflake-sdk@​2.4.1 ⏵ 2.4.3			+1
	npm/​@​keycardai/​mcp@​0.12.1 ⏵ 2.0.0	+1		+1	+1
	npm/​@​earendil-works/​pi-ai@​0.74.0 ⏵ 0.74.2			+1	+2
	npm/​@​modelcontextprotocol/​client@​2.0.0
	npm/​@​earendil-works/​pi-agent-core@​0.74.0 ⏵ 0.74.2	+2		+1
	npm/​@​modelcontextprotocol/​server@​2.0.0
	npm/​@​types/​node@​20.19.40 ⏵ 20.19.43			+1
	npm/​tsx@​4.23.9
	npm/​typebox@​1.1.38 ⏵ 1.3.11	+12
	npm/​@​a2a-js/​sdk@​0.3.13 ⏵ 0.3.14				+2
	pypi/​uvicorn@​0.51.0 ⏵ 0.52.1	+1
	pypi/​starlette@​1.3.1 ⏵ 1.4.1	+1
	pypi/​keycardai-mcp@​0.26.0 ⏵ 2.0.0	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm snowflake-sdk is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: autonomous-agent-snowflake-wif/package-lock.json → npm/snowflake-sdk@2.4.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/snowflake-sdk@2.4.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report