Skip to main content
Glama

Related Servers

Alternatives to MCP Servers

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript-based server project with comprehensive development tooling including testing, linting, and build configurations.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A production-grade MCP starter server in TypeScript with example tools, resources, and integration tests. It provides a clean, extensible foundation for building custom MCP servers.
      20 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript-based MCP server template using Express.js and Server-Sent Events, providing example tools for echoing messages, performing calculations, and retrieving server time.
      -
    • A
      license
      B
      quality
      D
      maintenance
      A template/boilerplate project for building Model Context Protocol (MCP) servers with TypeScript. Provides a starting point with configuration examples, development tools, and debugging setup.
      2
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A TypeScript starter template for building Model Context Protocol servers, enabling quick setup for custom tools and integration.
      20 npm
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A TypeScript MCP server boilerplate providing example tools and resources for rapid development and testing of Model Context Protocol servers.
      7
      -

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one provides current weather data, while the other provides a 5-day forecast. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the time horizon needed.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern with hyphens (get-current-weather, get-forecast). The naming is predictable and readable, with no deviations in style or convention across the set.

    Tool Count3/5

    With only 2 tools, the server feels thin for a weather domain, as it lacks operations like historical data, alerts, or location search. While the tools cover basic current and forecast needs, the count is borderline low for typical agent workflows that might require more comprehensive weather data.

    Completeness3/5

    The server provides core current and forecast functions, but there are notable gaps for a weather service, such as no historical weather data, severe weather alerts, or location autocomplete. Agents can work around this for basic queries, but the surface is incomplete for more advanced use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues