Skip to main content
Glama
coinselor

MCP Server Starter

by coinselor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to MCP Server Starter

No user-submitted related servers found.

    Related Servers

    • MCP Server Template

      berryj85
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready template for building Model Context Protocol servers using TypeScript and Bun runtime, including schema validation, structured logging, and retry utilities.
      4 npm
      MIT

    • MCP Boilerplate

      jhon2c
      A
      license
      Not graded
      quality
      D
      maintenance
      A modern, lightning-fast starter template for building Model Context Protocol applications with Bun, enabling developers to create MCP servers with TypeScript support, validation, and environment configuration.
      4 npm
      2
      MIT

    • Enterprise MCP Server Template

      qmmughal
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready TypeScript template for building Model Context Protocol (MCP) servers with Zod validation, structured logging, and seamless integration with AI agents like Claude Desktop and Cursor.
      24 npm
      4
      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

    C2.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The single tool's purpose is clearly distinct by default, eliminating any risk of misselection.

    Naming Consistency5/5

    The tool name 'hello_tool' follows a consistent snake_case pattern, and with only one tool, there is no inconsistency in naming conventions. The naming is straightforward and predictable within this minimal set.

    Tool Count2/5

    A single tool is generally too few for a server's purpose, as it suggests a very limited or trivial scope that may not support meaningful agent workflows. This is borderline for appropriateness, leaning toward insufficient coverage for typical MCP server use cases.

    Completeness1/5

    With only one tool named 'hello_tool', the server's domain is unclear, making it impossible to assess coverage meaningfully. There are likely significant gaps for any inferred purpose, as a single tool cannot provide CRUD/lifecycle operations or a coherent workflow, leading to severe incompleteness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources