Skip to main content
Glama
robertocirillo

mcp-elicitation-proxy

by robertocirillo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-elicitation-proxy

No user-submitted related servers found.

    Related Servers

    • Duck MCP Server

      theddnc
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides elicitation tools to interactively request user input, such as selecting options, providing information, or performing manual tests.
      3
      1
      MIT

    • MCP Elicitations Demo Server

      soriat
      A
      license
      C
      quality
      D
      maintenance
      A demonstration server that showcases how to collect user input dynamically using the Model Context Protocol (MCP) elicitation system across tools, resources, and prompts.
      10
      214,403 npm
      -

    • McpHub

      John0King
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.
      2
      MIT

    • AIMCP

      junqed
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that distributes tool specifications from GitLab repositories to IDEs, dynamically generating MCP tools and serving files via aimcp:// URIs.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 17 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources