Where cxxmcp is headed.
Current priorities, near-term plans, and longer-term goals.
Conformance parity with latest MCP spec (2026 draft)
In ProgressTrack and implement protocol changes from the 2026 spec draft. Already support all MCP spec versions: 2024-11-05, 2025-03-26, 2025-06-18, 2025-11-25, and DRAFT-2026-v1.
Stabilize public C++ SDK API surface
In ProgressLock down the Peer/Service/Transport/Protocol API contracts. Mark experimental features clearly.
Improve cross-platform build support
In ProgressWindows, Linux, macOS CI coverage. MinGW provisional compatibility tracked.
Automated dependency update tooling
Near TermDependabot or Renovate for third_party dependencies and GitHub Actions.
Publish exact-commit release evidence
Near TermAttach generated docs, release artifacts, checksums, compatibility notes, and package evidence from the exact tagged release run.
Improve test coverage for edge cases in transport layer
Near TermFocused tests for malformed input, connection drops, timeout edge cases, and concurrent requests.
Transport hardening
Longer TermMore stress, reconnect, and interop coverage for the built-in Streamable HTTP and WebSocket transports.
Full server and client implementation
DoneStreamable HTTP, SSE, stdio, and WebSocket transports. Complete protocol coverage.
OAuth 2.1 authorization support
DonePKCE, DPoP, JWKS, bearer tokens, metadata endpoints. Optional cxxmcp::auth target.
SEP-2243 header compliance
DoneMcp-Method and Mcp-Name headers validated when present. Filed issues on official SDKs for compliance.
109/110 server, 448/448 client conformance
DoneValidated against official modelcontextprotocol/conformance runner. The remaining server exception is documented in conformance evidence.