Elicitly
Human-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor
Open source Open in the app JSON README (API)
About
Human-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor
Details
- Kind
- MCP servers
- Topic
- No topic detected
- Publisher
- ai.elicitly
- Origin
- official
- Category
- ferramentas
- Transport
- local
- Version
- 0.7.2
- Stars
- 1
- Last push
- 2026-09-07T20:56:03Z
- Repository state
- ativo
- Language
- TypeScript
- License
- Apache-2.0
- Added
- 2026-08-29 03:00:11
- Updated
- 2026-09-07 21:05:06
- Origin id
ai.elicitly/elicitly
README
# Elicitly — Free Edition
[](https://www.npmjs.com/package/elicitly)
[](https://www.npmjs.com/package/@elicitly/tools)
[](https://www.elicitly.ai/docs/)
[](./LICENSE)
[](https://github.com/elicitly/elicitly/actions/workflows/ci.yml)
[](https://codecov.io/gh/elicitly/elicitly)
[](https://glama.ai/mcp/servers/elicitly/elicitly)
**Your AI has questions. Your users have answers.** Elicitly connects them —
human-in-the-loop for prompts and [Agent Skills](https://agentskills.io/) over
[MCP elicitation](https://modelcontextprotocol.io/docs/learn/client-concepts).
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](https://www.elicitly.ai).
## Quick start
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](https://github.com/elicitly/elicitly/releases/latest)
and open it — a one-click, self-contained
[desktop extension](./packages/elicitly/README.md#claude-desktop-one-click).
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?).
## Packages
| Package | What it is |
| --- | --- |
| [`elicitly`](./packages/elicitly) | The local stdio MCP server (`npx -y elicitly`) |
| [`@elicitly/tools`](./packages/tools) | Embeddable toolkit: register the elicitation tools on **your own** `McpServer` |
## Why
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](https://www.elicitly.ai/docs/elicitation/support-matrix/).
## Develop
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
## License
[Apache-2.0](./LICENSE)