mcp-elicitation-test
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-elicitation-testAsk the user what their favorite color is."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-elicitation-test
A minimal MCP (Model Context Protocol) stdio server whose sole purpose is to
raise elicitation requests (elicitation/create) from inside tool calls, so
that elicitation plumbing in MCP clients and agent platforms can be exercised
end-to-end.
Built as the test fixture for APT-798 — "Elicitation Requests from cagent
Background Jobs" on the Docker Agentic Platform, but it is a plain,
spec-conformant MCP server usable with any client that declares the
elicitation capability.
Tools
Tool | Elicitation | Purpose |
| none | Sanity check that the MCP server is wired up at all. |
| 1 string field | Single-question form elicitation. |
| string + boolean + enum + number | Multi-field form elicitation to exercise form-generation UIs across all primitive field types. |
All tools are annotated readOnlyHint: true / destructiveHint: false. This
matters: hosts that gate tool calls on destructiveness (docker-agent, the
Docker Agentic Platform) auto-approve read-only tools, and non-interactive
background contexts auto-deny any tool call that would need approval — so
without these annotations the elicitation would never even be raised from a
background job.
Every elicitation waits up to ELICIT_TIMEOUT_MS (default 1 hour) for the
human response. Each tool returns a JSON report (action, content,
waited_ms, timestamps) so the calling agent's transcript records exactly
what the elicitation round-trip produced.
Related MCP server: mcpbin
Run
npm install --omit=dev
node server.js # speaks MCP over stdioOr via the bin entry after npm install -g .: mcp-elicitation-test.
Smoke test
smoke-test.mjs spawns the server, declares the elicitation capability,
answers the elicitation programmatically, and prints the round-trip:
node smoke-test.mjsUsing from a docker-agent (cagent) config
agents:
root:
# ...
toolsets:
- type: mcp
command: node
args: ["/home/agent/mcp-elicitation-test/server.js"]See platform/ for the full test-agent YAML used for APT-798 end-to-end
testing on the Docker Agentic Platform (foreground, transfer_task, and
run_background_agent trigger paths).
License
Apache-2.0
This server cannot be deployed
Maintenance
Related MCP Connectors
POC MCP server. Tool say_hello returns 'Welcome' (agent -> MCP -> API path).
MCP server for progressive tool usage at any scale (see https://klavis.ai)
MCP server exposing the Backtest360 engine API as tools for AI agents.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- AlicenseCqualityDmaintenanceA demonstration server that showcases how to collect user input dynamically using the Model Context Protocol (MCP) elicitation system across tools, resources, and prompts.10214,403 npm-
- FlicenseNot gradedqualityDmaintenanceA testing server for MCP client implementations that provides tools for echoing data, error handling, timing operations, data generation, LLM sampling, and user elicitations.-
- AlicenseNot gradedqualityDmaintenanceA test MCP server that exercises all MCP protocol features, including prompts, tools, resources, and sampling, for client builders.214,403 npm-
- FlicenseAqualityCmaintenanceA minimal MCP server that demonstrates the entire protocol using a simple in-memory todo list, including tools, resources, prompts, and elicitation.31-