MCP Protocol Support

Supported today

The hosted Pro Edition speaks the MCP protocol from 2024-11-05 through 2026-07-28 — the newest published revision — on one endpoint, https://mcp.elicitly.ai/mcp:

• 2026-07-28 (stateless), natively. Requests carrying the revision’s per-request _meta envelope are served by a stateless handler built on the official TypeScript SDK v2: no initialize handshake, no session id, and elicitation via Multi Round-Trip Requests — elicit_confirm, elicit_form, and elicit_doctor return input_required and complete when your host retries with the answers. elicit_doctor fingerprints new-revision hosts natively, including a live MRTR elicitation probe.
• Earlier revisions (2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05), unchanged. Legacy hosts — which today means every shipping MCP host in the Support Matrix — get the sessionful transport they expect, including live URL-mode elicitation prompts. Nothing about their behavior changed.

The same twelve tools, with identical contracts, are served on both paths.

Why the approval flow didn’t have to change

Elicitly Pro was designed stateless-first from the start, ahead of the protocol: elicitation state is durable in Postgres, review pages work out-of-band on any device, and agents recover through polling (elicit_status / elicit_await / elicit_result) with no dependency on a live connection. The 2026-07-28 revision formalizes the same shape — ask, go away, come back for the answer — so the durable approval, selection, and proposal flows work identically on both revisions. (One deliberate difference: the best-effort URL-mode push was a legacy-revision server-initiated request, which 2026-07-28 removed — new-revision hosts discover completion by polling, which is what the flow was built on anyway.)

If anything, the new revision moves the protocol toward Elicitly’s premise: it exists specifically so that a tool can pause mid-call for human input — approving a destructive action, confirming a deploy — over connections that don’t stay open. That is the product. Elicitly adapts and evolves with the protocol; it is not tied to the revision it launched on.

The Free Edition

The open-source local server (npx -y elicitly) currently targets the v1 SDK line (2025-11-25). New-revision hosts are required by the spec to interoperate with earlier-revision servers, so it works everywhere today; its move to SDK v2 follows the hosted server’s.