Skip to main content
Glama
Mtar786

Example MCP Server

by Mtar786
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Example MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Server

      NavanethaKrishnan-14
      F
      license
      Not graded
      quality
      C
      maintenance
      A lightweight and extensible Model Context Protocol server built with Node.js, exposing custom tools and resources for AI clients.
      25
      -

    • MCP Boilerplate

      jakreymyers
      A
      license
      Not graded
      quality
      D
      maintenance
      A minimal, production-ready MCP server with a simple addition calculator tool that demonstrates integration with the Model Context Protocol.
      7
      1
      MIT

    • MCP Server Basic Example

      rezaeim
      A
      license
      Not graded
      quality
      D
      maintenance
      A basic implementation of a Model Context Protocol server that demonstrates core functionality with simple math tools (add, subtract) and greeting resources for AI assistants like Claude.
      GPL 3.0

    • MCP Calculator Server

      ayyappachinpandi
      F
      license
      Not graded
      quality
      D
      maintenance
      A minimal Model Context Protocol server that provides basic arithmetic tools and a comprehensive meeting analysis prompt template for processing transcripts. It serves as a clean example for developers to learn how to build, test, and integrate MCP servers with Claude Desktop.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one performs a mathematical addition operation on two numbers, while the other retrieves the current server time. There is no overlap or ambiguity between these functions, making it impossible for an agent to confuse them.

    Naming Consistency2/5

    The naming conventions are inconsistent: 'add' uses a simple verb form, while 'getTime' uses camelCase with a verb-object structure. This mixing of styles (no separator vs. camelCase) lacks a predictable pattern, though the names are still readable.

    Tool Count2/5

    With only two tools, the server feels thin and under-scoped for a general-purpose MCP server. This minimal set suggests limited functionality that might not cover basic workflows or domain needs effectively, making it borderline too few for practical use.

    Completeness1/5

    The tool surface is severely incomplete; it lacks any coherent domain coverage. The tools are unrelated (math and time), with no CRUD operations, lifecycle management, or logical connections, leaving significant gaps that would cause agent failures in most scenarios.

    Resources