Skip to main content
Glama
He110te4m

MCP Tool Starter Kit

by He110te4m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to MCP Tool Starter Kit

No user-submitted related servers found.

    Related Servers

    • MCP Template

      Mearman
      F
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript template for building Model Context Protocol servers that provides a structured foundation with automated tools, testing, and synchronization capabilities.
      6 npm
      -

    • MCP Server TypeScript

      LarouTech
      F
      license
      Not graded
      quality
      D
      maintenance
      A clean, reusable TypeScript boilerplate for building Model Context Protocol servers with support for custom tools and resources.
      12 npm
      -

    • MCP Server Template

      stevennevins
      A
      license
      C
      quality
      D
      maintenance
      A TypeScript-based template for developing Model Context Protocol servers with features like dependency injection and service-based architecture, facilitating the creation and integration of custom data processing tools.
      1
      8 npm
      4
      ISC
    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

    C2.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'getUserInfo' follows a clear verb_noun pattern.

    Tool Count2/5

    A single tool is too few for a server named 'MCP Tool Starter Kit', which implies a broader or introductory set of tools. This minimal count feels incomplete and mismatched with the expected scope.

    Completeness2/5

    The tool surface is severely incomplete; 'getUserInfo' alone cannot cover any meaningful domain or workflows. There are significant gaps, such as lacking create, update, delete, or other related operations, making it inadequate for practical use.

    Resources