Elicitly MCP server
{
"mcpServers": {
"elicitly": {
"command": "npx",
"args": [
"-y",
"elicitly@latest"
]
}
}
}{
"mcpServers": {
"elicitly": {
"command": "npx",
"args": [
"-y",
"elicitly@latest"
]
}
}
}{
"mcpServers": {
"elicitly": {
"command": "npx",
"args": [
"-y",
"elicitly@latest"
]
}
}
}{
"servers": {
"elicitly": {
"command": "npx",
"args": [
"-y",
"elicitly@latest"
]
}
}
}{
"mcpServers": {
"elicitly": {
"command": "npx",
"args": [
"-y",
"elicitly@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y elicitlyversion 0.7.2
What it does
Elicitly is an MCP server that enables human-in-the-loop interactions for AI agents using the MCP elicitation protocol. It exposes tools for confirmation dialogs, custom forms, and capability diagnostics, targeting developers who need to pause agent workflows for user input.
- Ask a user to confirm an action before an agent proceeds, such as approving a deployment.
- Present a custom form to a user during an agent workflow using a JSON schema definition.
- Diagnose whether the connected MCP host actually supports elicitation before relying on it.
Tools this server exposes
| Tool | Does |
|---|---|
| elicit_confirm | Presents a yes/no confirmation dialog to the user and returns their response. |
| elicit_form | Presents a custom form defined by a JSON schema to the user and returns the filled values. |
| elicit_doctor | Checks whether the current MCP host supports elicitation and reports the result. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.