Human-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor
Your AI has questions. Your users have answers. Elicitly connects them — human-in-the-loop for prompts and Agent Skills over MCP elicitation.
This repository is the open-source Free Edition: the elicitly local MCP
server and the @elicitly/tools library. The hosted Pro Edition — durable
approvals with review pages, an audit trail, and organization dashboards —
lives at elicitly.ai.
Run the local (stdio) MCP server straight from npm — no clone, no config:
npx -y elicitly
Register it in your MCP host (Claude Code shown; any stdio host works):
claude mcp add elicitly -- npx -y elicitly
Or skip the command line: in Claude Desktop, download elicitly.mcpb from
the latest release
and open it — a one-click, self-contained
desktop extension.
Then ask your agent to call elicit_confirm ("Ship it?"), elicit_form
(your own JSON schema), or elicit_doctor (does this host actually support
elicitation?).
| Package | What it is |
|---|---|
elicitly | The local stdio MCP server (npx -y elicitly) |
@elicitly/tools | Embeddable toolkit: register the elicitation tools on your own McpServer |
MCP has a native answer for asking a human — elicitation — but host support is
inconsistent, and only an MCP server can trigger it. Nobody wants to roll
their own server just to ask a question. Elicitly is that server (or, via
@elicitly/tools, the toolkit inside yours), plus the diagnostic
(elicit_doctor) that makes real-world host support visible — feeding the
public Support Matrix.
pnpm install
pnpm build # tsdown builds both packages
pnpm test # vitest
pnpm test:coverage # vitest + v8 coverage (thresholds enforced; HTML report in coverage/)
pnpm typecheck # tsc
pnpm check # biome
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y elicitlyMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"ai-elicitly-elicitly": {
"command": "npx",
"args": [
"-y",
"elicitly"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceelicitlynpmElicitly works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.