This file records the current support boundary for ModelContextProtocol.jl.
The dated protocol guides in the published MCP specification are the source of
truth for wire behavior.
The package supports Streamable HTTP for two protocol eras:
- MCP
2025-11-25: stateful initialization, sessions, resumable server event streams, cancellation, ping, logging level changes, resource subscriptions, tools, prompts, resources, completions, and MCP Apps. - MCP
2026-07-28: stateless request metadata,server/discover, standard and custom request headers, bounded supported-version retries for ordinary HTTP calls, cache metadata, client capability checks, multi-round-tripinput_requiredresults, request-scoped progress and log events, andsubscriptions/listen. - Experimental MCP Events webhook profile on
2026-07-28: event discovery, owner-scoped idempotent subscriptions, finite TTLs, durable subscription storage, callback verification, Standard Webhooks HMAC signing and rotation, filtering, access rechecks, bounded retries, and client helpers.
The general server accepts both versions by default. The client defaults to
2025-11-25. Applications opt in to 2026-07-28 with MCPClientConfig.
The client also owns local child processes through
ModelContextProtocol.prepare_stdio_client. It supports newline-delimited
JSON-RPC, concurrent calls, notifications, legacy server requests, cancellation,
and bounded process shutdown for either explicitly selected protocol version.
Notifications retain arrival order; bounded legacy request-handler tasks allow
nested calls and may overlap notifications and other request handlers.
The package also includes a separate server for JuliaC --trim=safe builds.
It serves tools, fixed resources, and MCP Apps metadata, with an optional
session-free mode. That server intentionally supports only the documented
2025-11-25 subset.
The repository tests these areas:
- Julia 1.10, current stable Julia, and Julia nightly on Linux, macOS, and Windows.
- OAuth 2 and OAuth 3 compatibility.
- Stateful and stateless HTTP client/server integration.
- Legacy event streams and session cleanup on either server preference, with modern session operations, unsupported versions, and invalid origins rejected.
- Headerless legacy initialization, handlers that use the request's version, continued modern and subsequent-request header enforcement, and bounded version retries that preserve request data without replaying unrelated errors.
- Owned stdio child processes, concurrent response correlation, malformed or oversized frames, cancellation, nested server requests, bounded callback tasks, blocked callbacks, concurrent callback close, and process shutdown.
- Strict JSON-RPC parsing and notification side-effect rules.
- Client result response IDs must match the request before results or session state are accepted.
- MCP Apps resource and tool metadata.
- Official MCP conformance scenarios for stateless metadata, capability
checks, standard request headers, and
x-mcp-headerbehavior. - Modern tool calls use the same serialized arguments for custom headers and the request body, including custom JSON lowering and duplicate object keys.
- JuliaC trim compilation for the static server.
- Documenter build and doctests.
- Seeded event request, identity, signature mutation, and lifecycle fuzzing; callback address policy and DNS rebinding; authenticated HTTP lifecycle; restart recovery; pinned HTTPS delivery, TLS hostname checks, and redirects.
- Stdio is a client transport only. It does not provide a stdio server, protocol auto-detection, automatic restart/replay, modern subscriptions, HTTP headers/OAuth, or automatic Agentif tool-catalog import. Callbacks must cooperate with shutdown; a blocked callback produces an explicit close error.
- The general client, including subprocess stdio, is not a JuliaC trim-safe API. The separate static server remains the supported native subset.
- Tool input and output schemas are advertised but are not a complete runtime JSON Schema validation engine. A handler must still validate domain rules.
- Event validation uses JSONSchema.jl drafts 4, 6, and 7. Portable implicit schemas are advertised without a dialect for MCP's default 2020-12; explicit dialects and other implicit schemas retain their legacy declarations. This is not a general 2020-12 validator. Delivery is webhook-only and synchronous. No polling, push, replay, dynamic catalog notifications, durable outbox, or gap/termination envelopes are implemented. Subscriptions always have finite lifetimes.
- The file event store has one process owner. Replicas need a shared transactional backend and distributed coordination.
- Modern request-scoped progress and log events keep their correct order, but the server buffers them until the handler returns.
- Modern sampling, roots, and elicitation are exposed as multi-round-trip input requests. The application performs the external interaction and retries the original MCP request.
- OAuth helpers do not implement every optional proof-of-possession mechanism.
- The static JuliaC server does not support prompts, resource templates,
resource subscriptions, embedded resources in tool results, OAuth, arbitrary
middleware, or the
2026-07-28protocol. Its stateless mode still uses the2025-11-25initializehandshake.
- Add the official MCP conformance runner to CI when its
2026-07-28package release is stable. - Stream modern request-scoped events while a handler is still running.
- Add a standard client API that closes one
subscriptions/listenstream without ending the server. - Evaluate a lightweight JSON Schema validator for tool arguments and structured results.
Do not add a feature only to increase surface coverage. Preserve the small
export surface. Keep specialized helpers under the ModelContextProtocol
namespace.