mcp-elicitation-test
Click on "Install 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: MCP Elicitations Demo Server
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 installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/simonferquel-clanker/mcp-elicitation-test'
If you have feedback or need assistance with the MCP directory API, please join our Discord server