Skip to main content
Glama
gemyago

HelloWorld MCP Server

by gemyago
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

HelloWorld MCP Server

A simple HelloWorld MCP (Model Context Protocol) server experiment built with TypeScript.

Features

This MCP server provides two simple tools:

  • hello: Say hello to someone (default: "World")

  • add: Add two numbers together

Related MCP server: Example MCP Server

Prerequisites

  • Node.js 22+ (LTS)

  • npm

  • nvm (recommended for Node.js version management)

  • direnv (for environment management)

Setup

  1. Node.js Version Management

    # If you have nvm installed:
nvm use

# This will use Node.js version 22 as specified in .nvmrc

  2. Environment Setup with direnv

    # Allow direnv for this directory
direnv allow

# This will automatically add node_modules/.bin to your PATH

  3. Install Dependencies

    npm install

Development

Available Scripts

  • npm run dev - Run the server in development mode using tsx

  • npm run build - Compile TypeScript to JavaScript

  • npm start - Run the compiled server

  • npm run lint - Run ESLint on the source code

  • npm run lint:fix - Run ESLint and automatically fix issues

  • npm run clean - Remove the dist directory

Running the Server

For development:

npm run dev

For production:

npm run build
npm start

MCP Server Usage

This server communicates via stdio and implements the Model Context Protocol. It provides:

Tools

  1. hello

    • Description: Say hello to someone

    • Parameters:

      • name (optional): The name of the person to greet (default: "World")

    • Example: {"name": "Alice"} → "Hello, Alice! 👋 Welcome to the HelloWorld MCP server!"

  2. add

    • Description: Add two numbers together

    • Parameters:

      • a (required): First number

      • b (required): Second number

    • Example: {"a": 5, "b": 3} → "5 + 3 = 8"

Project Structure

├── src/
│   └── index.ts          # Main MCP server implementation
├── dist/                 # Compiled JavaScript (after build)
├── .nvmrc               # Node.js version specification
├── .envrc               # direnv configuration
├── eslint.config.js     # ESLint configuration
├── tsconfig.json        # TypeScript configuration
├── package.json         # Node.js project configuration
└── README.md           # This file

Code Quality

This project uses:

  • TypeScript for type safety

  • ESLint with TypeScript support for code quality

  • Strict TypeScript configuration for better type checking

License

MIT

Available Tools

2 tools
addB

Add two numbers together

ParametersJSON Schema
NameRequiredDescriptionDefault
aYesFirst number
bYesSecond number

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Add two numbers together' implies a simple computation but doesn't disclose any behavioral traits like error handling, precision limits, or return format. It's minimal and lacks context about what the tool actually does beyond the basic operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise ('Add two numbers together')—a single sentence that front-loads the core purpose with zero waste. Every word earns its place, making it highly efficient and well-structured for its simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (simple arithmetic), no annotations, no output schema, and high schema coverage, the description is minimally adequate. It states what the tool does but lacks details on behavior or output, making it complete enough for basic understanding but with clear gaps for an agent needing full context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage with clear parameter descriptions ('First number', 'Second number'), so the baseline is 3. The description 'Add two numbers together' aligns with the schema but doesn't add meaningful semantic context beyond what's already documented in the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Add two numbers together' clearly states the verb ('add') and resource ('two numbers'), making the purpose immediately understandable. However, it doesn't distinguish from sibling tools (only 'hello' exists, which is unrelated), so it doesn't fully meet the highest standard of sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions. While the sibling tool 'hello' is unrelated, there's no explicit comparison or usage context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

helloB

Say hello to someone

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the person to greetWorld

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Say hello to someone' implies a read-only, non-destructive action, but it doesn't specify whether this requires authentication, has rate limits, returns structured data, or how the greeting is delivered (e.g., console output, API response). For a tool with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple greeting tool. Every word earns its place without redundancy or unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavioral traits, usage context, or output format. For such a simple tool, this might be sufficient, but it doesn't provide complete guidance for optimal agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the single parameter 'name' fully documented in the schema as 'The name of the person to greet' with a default value. The description doesn't add any parameter details beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Say hello to someone' clearly states the tool's purpose with a specific verb ('say hello') and target ('to someone'). It distinguishes from the sibling tool 'add' which likely performs a different function. However, it doesn't specify the exact output format or delivery mechanism, keeping it from a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or comparisons with the sibling tool 'add'. The agent must infer usage solely from the tool name and description without explicit direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updates
    • First observedadd
    • First observedhello
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: 'add' performs a mathematical operation on numbers, while 'hello' handles a greeting interaction. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.

Naming Consistency5/5

Both tool names are simple, lowercase verbs ('add' and 'hello') that clearly indicate their actions. While they don't follow a strict verb_noun pattern, the naming is perfectly consistent in style and readability for this minimal set.

Tool Count2/5

With only two tools, this server feels extremely thin and under-scoped for any meaningful domain. The tools are trivial and unrelated, suggesting either a demo/test server or one with significant missing functionality for practical use.

Completeness1/5

The server lacks a coherent domain, making completeness impossible to assess meaningfully. The tools are isolated operations (math and greeting) with no logical connection or coverage of any workflow, representing a severely incomplete surface for any real-world purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP Calculator Server

    Aditya24023022
    A
    license
    Not graded
    quality
    D
    maintenance
    A lightweight TypeScript-based MCP server that demonstrates how to build custom MCP tools by implementing a simple addition calculator. Serves as a starting point for building MCP-compatible tools.
    887
    MIT

  • Example MCP Server

    jherr
    A
    license
    Not graded
    quality
    D
    maintenance
    A simple demonstration MCP server that provides a basic 'say_hello' tool for greeting users by name, serving as a template for building MCP servers with TypeScript.
    7
    1
    ISC

  • mcp-hello-typescript-server

    mitchallen
    A
    license
    A
    quality
    A
    maintenance
    A minimal MCP server that provides a health check (server_info) and multi-language greeting (greet) tools, built with TypeScript and the official SDK.
    2
    MIT

  • Dev Tools MCP Server

    DRX-1877
    F
    license
    Not graded
    quality
    D
    maintenance
    A TypeScript MCP server example providing basic developer tools: hello world greeting, arithmetic calculator, and file information retrieval.
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gemyago/typescript-mcp-boilerplate'

If you have feedback or need assistance with the MCP directory API, please join our Discord server