Skip to content

v0.3.0 — MCP Auth Server Template

Choose a tag to compare

@brunovicco brunovicco released this 09 Aug 19:29
· 16 commits to main since this release
418d642

v0.3.0 — MCP Auth Server Template

v0.3.0 advances the authentication reference pair with executable MCP 2026 interoperability.

Use this release with mcp-client-auth-template v0.3.0 for the tested cross-repository profile.

Highlights

  • MCP 2026-07-28 modern request-envelope validation.
  • Sessionless Streamable HTTP semantics.
  • Protocol-version and routing-envelope mismatch handling.
  • Runtime scope step-up for protected MCP tools.
  • Client ID Metadata Document-first interoperability.
  • OAuth Client Credentials extension advertisement.
  • Generic OIDC machine-to-machine authentication support at the resource-server boundary.
  • Positive and negative cross-repository compatibility evidence.
  • Architecture decisions documented in ADRs 0015 through 0018.

Security model

  • Extension negotiation is capability discovery, not authorization.
  • Access still requires a validated, audience-bound, issuer-bound, unexpired token with sufficient
    scopes.
  • The MCP server does not issue tokens, receive client secrets, or persist OAuth credentials.
  • Generic machine identities remain distinct from Microsoft Entra application principals.
  • Protocol, request-envelope, credential, and authorization failures remain fail closed.

Compatibility

  • Python: >=3.13,<3.15
  • MCP Python SDK: >=2.0,<3
  • MCP SDK tested floor: 2.0.0
  • MCP protocol reference: 2026-07-28
  • Transport: Streamable HTTP
  • Authentication: Microsoft Entra ID and generic OIDC
  • Companion release: mcp-client-auth-template v0.3.0

Validation

  • Complete quality and security gate
  • Python 3.13 and 3.14 compatibility matrix
  • MCP SDK 2.0.0 and latest compatible 2.x
  • Cross-repository contract validation
  • Companion OAuth/MCP E2E suite: 12 scenarios