Free Edition
@elicitly/local is a local (stdio) MCP server that makes MCP elicitation easy
to test and its cross-host support visible. It exposes three tools — DOCTOR,
ELICIT_FORM, and CONFIRM — and is open source.
This page mirrors the package
README.md. If they diverge, the README is the source of truth for tool behavior.
Install & run (published artifact)
Section titled “Install & run (published artifact)”Once published, run it straight from npm — no clone required:
npx -y @elicitly/localRegister it with any MCP host as a stdio server. In Claude Code:
claude mcp add elicitly -- npx -y @elicitly/localOr add it to a host config file (.mcp.json or client settings):
{ "mcpServers": { "elicitly": { "command": "npx", "args": ["-y", "@elicitly/local"] } }}Run it locally (from source)
Section titled “Run it locally (from source)”For development — or to try it before anything is published — install and build the CLI, then point your host at the compiled entry:
pnpm installpnpm --filter @elicitly/local build # produces apps/local/dist/cli.jsThe repo ships a top-level .mcp.json that already points Claude Code at that
build; from the repo root, start Claude Code and approve the elicitly server when
prompted:
claude # auto-discovers .mcp.jsonPrefer to register it yourself, or use a different stdio host? Point it at the built file with an absolute path:
claude mcp add elicitly -- node /absolute/path/to/apps/local/dist/cli.jsAfter editing the source, rebuild (pnpm --filter @elicitly/local build) and
restart the server in your host.
Next steps
Section titled “Next steps”- Tools reference —
DOCTOR,ELICIT_FORM,CONFIRMwith example inputs and outputs. - Elicitation Support Matrix — what real hosts actually support.