mcp-elicitation-proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ELICITATION_PROXY_CONFIG | No | Path to the configuration YAML file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Echoes back the input string |
| get-annotated-messageC | Demonstrates how annotations can be used to provide metadata about content. |
| get-envA | Returns all environment variables, helpful for debugging MCP server configuration |
| get-resource-linksA | Returns up to ten resource links that reference different types of resources |
| get-resource-referenceC | Returns a resource reference that can be used by MCP clients |
| get-structured-contentB | Returns structured content along with an output schema for client data validation |
| get-sumA | Returns the sum of two numbers |
| get-tiny-imageA | Returns a tiny MCP logo image. |
| gzip-file-as-resourceA | Compresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request during the current session. |
| toggle-simulated-loggingA | Toggles simulated, random-leveled logging on or off. |
| toggle-subscriber-updatesA | Toggles simulated resource subscription updates on or off. |
| trigger-long-running-operationB | Demonstrates a long running operation with progress updates. |
| get-roots-listA | Lists the current MCP roots provided by the client. Demonstrates the roots protocol capability even though this server doesn't access files. |
| trigger-elicitation-requestC | Trigger a Request from the Server for User Elicitation |
| trigger-url-elicitationA | Trigger a URL elicitation so the client can direct the user to a browser flow. Supports two mechanisms: the request path (elicitation/create, default) which awaits the user's response, and the error path (UrlElicitationRequiredError, -32042) which signals the client to handle URL elicitation via the error response. Set errorPath=true to use the error path. |
| trigger-sampling-requestC | Trigger a Request from the Server for LLM Sampling |
| simulate-research-queryA | Simulates a deep research operation that gathers, analyzes, and synthesizes information. Demonstrates MCP task-based operations with progress through multiple stages. If 'ambiguous' is true and client supports elicitation, sends an elicitation request for clarification. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| simple-prompt | A prompt with no arguments |
| args-prompt | A prompt with two arguments, one required and one optional |
| completable-prompt | First argument choice narrows values for second argument. |
| resource-prompt | A prompt that includes an embedded resource reference |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| architecture.md | Static document file exposed from /docs: architecture.md |
| extension.md | Static document file exposed from /docs: extension.md |
| features.md | Static document file exposed from /docs: features.md |
| how-it-works.md | Static document file exposed from /docs: how-it-works.md |
| instructions.md | Static document file exposed from /docs: instructions.md |
| startup.md | Static document file exposed from /docs: startup.md |
| structure.md | Static document file exposed from /docs: structure.md |
TDQS
Scored across 17 tools
Most tools have distinct purposes, but there is overlap among trigger-type tools (trigger-elicitation-request, trigger-url-elicitation, trigger-sampling-request) and simulation tools that also involve elicitation (simulate-research-query). Additionally, 'get-resource-links' and 'get-resource-reference' could be confused despite their clear descriptions.
All tool names consistently use a hyphenated verb-noun pattern (e.g., get-env, toggle-logging, trigger-elicitation-request). There are no mixed conventions or inconsistencies.
With 17 tools, the server sits at the upper edge of a reasonable scope. Many tools are demonstrations of MCP features (echo, get-sum, gzip-file-as-resource) alongside core elicitation/simulation, making the count feel slightly heavy but not excessive.
The server covers a wide range of MCP capabilities including elicitation, sampling, resources, logging, subscriptions, roots, and long-running operations. Minor gaps exist (e.g., no explicit tool to query elicitation status), but the surface is adequate for a demonstration/proxy server.