Skip to content

Bump fastmcp to 3.4.7 (stay on MCP v1 line) - #13

Open
Superagentic-AI wants to merge 1 commit into
mainfrom
chore/fastmcp-3.4.7
Open

Superagentic-AI wants to merge 1 commit into
mainfrom
chore/fastmcp-3.4.7

Conversation

@Superagentic-AI

Copy link
Copy Markdown
Contributor

Summary

  • Pin fastmcp 3.4.43.4.7 and refresh uv.lock (fastmcp-slim follows).
  • Refresh the dependency comment: MCP SDK v2 and FastMCP 4 are stable now, but SuperQode still intentionally stays on the v1 / 3.x line until a planned migration.

Why

Weekday ecosystem watch (2026-09-04): clear small win on the existing MCP stack. 3.4.5–3.4.7 are patch fixes (JWKS unsupported-key skip, trusted-proxy SSRF path, CIMD private_key_jwt audience).

Not in this PR

  • No jump to FastMCP 4 / mcp v2 (larger migration).
  • No agent-client-protocol 0.12 lift (still capped <0.12; needs compatibility work).
  • A2A SDK 1.1.3 is tagged on GitHub but not on PyPI yet; UHP remains 2026-08-11.

Test plan

  • uv sync (or CI) resolves fastmcp==3.4.7
  • Existing MCP / FastMCP smoke paths still import and run

Stay on FastMCP 3 / MCP SDK v1; pull patch fixes through 3.4.7
(JWKS key skip, proxy SSRF path, CIMD audience) without migrating
to FastMCP 4 / MCP v2 yet.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant