Skip to main content
Glama
ivanbtrujillo

MCP Server Example

Related Servers

Alternatives to MCP Server Example

No user-submitted related servers found.

    Related Servers

    • F
      license
      C
      quality
      D
      maintenance
      A starter template for building MCP servers that can integrate with Claude, Cursor, or other MCP-compatible AI assistants to create custom tools, resource providers, and prompt templates.
      2
      12 npm
      -
    • F
      license
      A
      quality
      D
      maintenance
      A starter template for building custom MCP servers that can integrate with Claude Desktop, Cursor, and other AI assistants. Provides example tools, TypeScript support, and automated publishing workflows to help developers create their own AI assistant integrations.
      7
      4 npm
      -
    • F
      license
      A
      quality
      D
      maintenance
      A starter template for building custom MCP servers that can integrate with Claude Desktop, Cursor, and other AI assistants. Provides example tools, TypeScript support, and automated publishing workflows to help developers quickly create their own MCP servers.
      7
      4 npm
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A starter template for building MCP servers that enable AI assistants to interact with custom tools and data.
      8 npm
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A demo MCP server built with FastMCP that provides weather, calculation, and currency conversion tools for use with AI applications like Claude Desktop and Cursor.
      3
      -

    TDQS

    B3.1/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 for alerts versus forecasts.

    Naming Consistency5/5

    Both tools follow a consistent verb-noun pattern with hyphens (get-alerts, get-forecast), using the same verb 'get' and descriptive nouns. This predictable naming scheme enhances readability and reduces confusion for agents.

    Tool Count2/5

    With only two tools, the server feels thin for a weather domain that typically involves more operations, such as current conditions, historical data, or radar imagery. This limited set may not fully support comprehensive weather-related tasks.

    Completeness2/5

    The tool set is severely incomplete for a weather server, lacking essential operations like getting current conditions, historical weather data, or radar images. This creates significant gaps that could lead to agent failures in handling broader weather queries.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues