Skip to main content
Glama
YunYouJun

Starter MCP Server

by YunYouJun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Starter MCP Server

No user-submitted related servers found.

    Related Servers

    • TypeScript MCP Server

      leon4652
      F
      license
      B
      quality
      D
      maintenance
      A boilerplate project for quickly developing Model Context Protocol (MCP) servers using TypeScript, including example tools and resources to get started.
      4
      -

    • TypeScript MCP Server

      jeena-9595
      F
      license
      Not graded
      quality
      D
      maintenance
      A template project for quickly building Model Context Protocol (MCP) servers using TypeScript and the official SDK. It includes pre-configured examples for tools and resources to help developers jumpstart their custom MCP server development.
      25 npm
      -

    • toni-mcp-server

      toni0402-han
      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
      -

    • my-mcp-server

      Gwyn-Ahchoo
      F
      license
      B
      quality
      D
      maintenance
      A TypeScript MCP server boilerplate providing example tools and resources for rapid development of custom Model Context Protocol servers.
      8
      -

    • MCP TypeScript Template

      nickytonline
      A
      license
      Not graded
      quality
      A
      maintenance
      A starter template for building remote Model Context Protocol servers using TypeScript, providing modern tooling and best practices while leveraging the MCP TypeScript SDK.
      56
      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

    B3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves weather alerts for a state, and the other retrieves weather forecasts for a location. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the need.

    Naming Consistency4/5

    Both tools follow a consistent verb_noun pattern with 'get' as the verb, but they use kebab-case (get-alerts, get-forecast) instead of the more common snake_case. This minor deviation is still readable and predictable, though not perfectly aligned with typical conventions.

    Tool Count2/5

    With only 2 tools, the server feels thin for a weather domain that could include more operations like historical data, radar images, or air quality. While it covers basic alerts and forecasts, the scope is limited and may not support comprehensive agent workflows.

    Completeness2/5

    The tool set is severely incomplete for a weather server, lacking essential operations such as current conditions, historical data, or multi-day forecasts. Agents will face dead ends when trying to perform common weather-related tasks beyond the two provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources