The hosted Agiler MCP server now supports the stateless protocol model introduced in the MCP 2026-07-28 specification release candidate.
With the new protocol revision, every JSON-RPC request is a self-contained POST. Clients no longer have to open a protocol session with an initialize handshake, retain an Mcp-Session-Id, or return to the server instance that created that session. Protocol version, client information, and capabilities travel with each request, and clients can use server/discover to inspect the server before making a tool call.
Why stateless MCP matters
Removing protocol sessions makes MCP traffic behave more like an ordinary HTTP API. Any Agiler MCP request can be handled by any available server instance, without sticky routing or a shared session store. That makes horizontal scaling and rolling deployments simpler, and a client is not tied to transport state held by one process.
It also fits Agiler’s authorization model better. The server verifies the API key and rebuilds the tools available to it on every request. If a key is revoked or one of its scopes changes, that update applies on the very next call. Each tools/list response is marked private with a zero-second cache lifetime so a client can always refresh the catalog without reusing another credential’s view.
Stateless here describes the MCP transport, not the work an agent performs. Agiler projects, files, backups, and other resources remain persistent. Longer-running SQL and WP-CLI operations still return explicit IDs that an agent can use in later calls; that state is part of the operation rather than hidden inside a transport session.
What changes for clients
Clients that support MCP 2026-07-28 can use the stateless flow immediately. They send the protocol and operation metadata with each request and no longer receive or send an Mcp-Session-Id. Request-scoped Server-Sent Events responses remain available when a call needs streaming, but there is no separate resumable event stream to maintain between calls.
The endpoint and authentication setup have not changed:
https://mcp.agiler.io/v1
Continue to send an Agiler API key as a bearer token. Existing clients that still use the older initialize flow are accepted for compatibility, while newer clients can use server/discover and independent requests. No API key changes or MCP configuration updates are required.
Stateless MCP support is available now across the full Agiler MCP tool catalog. See the MCP reference for protocol details, client setup, scopes, and the complete tool list.