Skip to main content
Glama
leestott

mcpdemos

by leestott

Related Servers

Alternatives to mcpdemos

No user-submitted related servers found.

    Related Servers

    • 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.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables developers to build, run locally with debugging, and deploy to the cloud custom remote MCP endpoints hosted on Azure Functions, with built-in Microsoft Entra authentication. Sample projects demonstrate snippet CRUD and QR code tools, resource templates, prompt workflows, and an interactive weather demo UI.
      -
    • F
      license
      Not graded
      quality
      B
      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
      -
    • A
      license
      Not graded
      quality
      D
      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.
      9 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Publishes sample Python implementations that expose tools such as snippet CRUD, QR code generation and batch operations, resources, and prompts like code review checklists and doc generation, plus an interactive weather app, to MCP clients. These can be run locally with debugging or deployed to Azure with built-in Microsoft Entra authentication.
      -

    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