Skip to main content
Glama
leestott

mcpdemos

by leestott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcpdemos

No user-submitted related servers found.

    Related Servers

    • mcp-server-demo

      gandhips-Perry
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients to connect to example tools, resources, and prompts over MCP, demonstrating integration with IDEs, chatbots, and agent frameworks.
      -

    • UI5con 2026 MCP Apps

      marianfoo
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides runnable samples demonstrating how MCP tools can return deterministic, interactive UIs using HTML, UI5 Web Components, UI Integration Cards, and host-orchestrated SAP transport data.
      10
      -

    • mcp-demo

      EslamElshaabany
      A
      license
      Not graded
      quality
      B
      maintenance
      A demo MCP server showcasing every MCP capability with fake logic, including tools, resources, prompts, progress, cancellation, elicitation, sampling, roots, and subscriptions, over Streamable HTTP, HTTP+SSE, and stdio transports.
      10 npm
      MIT

    • mCP 2.0

      weijianzhg
      F
      license
      Not graded
      quality
      B
      maintenance
      Demonstrates stateful application patterns on the stateless MCP 2026-07-28 protocol, enabling request-scoped state, multi round-trip confirmations, and streaming progress updates across independent tool calls.
      -

    • sign-in-form

      krasnoff
      F
      license
      A
      quality
      C
      maintenance
      This MCP server enables MCP Apps-compatible hosts to render an interactive React-based UI and invoke a sample tool over streamable HTTP or stdio transports.
      1
      -
    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

    A3.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct demo scenario and action, with no overlapping purposes. The demoX prefix clearly groups related tools, and individual tool descriptions specify unique roles (e.g., start vs. confirm vs. check progress).

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (e.g., demo1_polite_cli, demo2_scaffold_start, demo3_request_consent). The naming is uniform across all 16 tools with no deviations.

    Tool Count4/5

    With 16 tools, the count is slightly above the ideal 3-15 range, but given the multi-demo scope, it remains well-scoped. Each tool serves a distinct purpose, and none feel redundant.

    Completeness4/5

    The tool surface covers the core workflows for each demo scenario (e.g., scaffolding, consent flow, pipeline management, palette operations). Minor gaps exist (e.g., no tool to reset a demo), but overall it supports the intended demonstrations adequately.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources