Pro Edition

The Pro Edition makes human-in-the-loop easy for prompts and skills. Agents increasingly take consequential actions — deploys, payments, destructive changes — and the step that needs a human (“may I?”) should be one tool call in your skill, not bespoke plumbing rebuilt for every workflow.

Why hosted?

MCP has a native answer for asking a human — elicitation — but host support is not yet consistent: form mode is uneven across hosts (see the Support Matrix), and URL mode is new in the 2025-11-25 spec revision. Waiting for every host to catch up means shipping nothing today; coding to the lowest common denominator means nothing improves tomorrow.

The Pro Edition is the adaptive middle. Your skill always makes the same three calls — elicit_approval → elicit_await → elicit_result — and the server adapts underneath: it pushes a native URL-mode prompt to hosts that advertise support for it, and every host (capable or not) reaches the same outcome through a hosted review page and long-poll. It works today, and it gets better as hosts adopt the spec — without changing your skill.

Being hosted is also what makes approvals trustworthy:

• Authenticated — every session is tied to a signed-in user and organization.
• Persisted and auditable — each request and every decision/fetch is recorded; the reviewer approves — or fills in — the exact data that will run.
• TTL-bounded — approvals expire; nothing waits forever.
• Everything in Free included — the hosted server also exposes elicit_doctor, elicit_form, and elicit_confirm, so upgrading is a migration to one endpoint, not a second server to run.

Beyond the form dialog

Basic form elicitation asks a question; Pro runs a process. Approval requests get a message, a review page, and an expiry. Decisions survive disconnects and reach reviewers wherever they are — native prompt or browser. Every request, decision, and fetch lands in an audit trail your team can actually read. It’s a more sophisticated human-in-the-loop experience for the people on both ends of the question — your users will thank you.

Next steps

• Install — sign up and register the hosted endpoint in your MCP host.
• Approval Flow — how a request plays out, end to end.
• Selection Flow — ask a human to pick from a list (disambiguation, choose-one/many).
• Proposal Flow — review, edit, and selectively approve a proposed record create-or-update as a multi-source diff grid.
• Templates — how your LiquidJS templates render: the engine, JavaScript-style truthiness, escaping, and limits.
• Rate Limiting — the per-org and per-user limits on tool calls, and what a throttled response looks like.
• Data Retention — how long requests, decisions, and form submissions are kept, and what the daily purge deletes.
• Tools reference — every tool’s contract, badged Free or Pro.