Skip to main content
Glama
niellevince

hello-world-mcp

by niellevince
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

Hello World MCP Server

A simple Model Context Protocol (MCP) server that provides a hello world tool. This server serves as a boilerplate template to help developers quickly create and deploy new MCP servers. It demonstrates basic MCP server functionality with a greeting tool and can be easily modified to add custom tools and resources.

Features

  • Hello World Tool: Simple greeting tool that says "Hello, {name}" with default "world"

  • Input Validation: Uses Zod schemas for robust parameter validation

  • Simple and Clean: Minimal MCP server implementation for demonstration purposes

Related MCP server: Hello World MCP Server

Using as a Boilerplate

This project serves as a starting template for building your own MCP servers. To create a custom MCP server:

  1. Clone or fork this repository

  2. Modify index.js to add your own tools using server.registerTool()

  3. Update package.json with your server name and description

  4. Customize the README and configuration files as needed

The basic structure includes proper error handling, input validation with Zod, and MCP protocol compliance.

Hello World Tool

The server provides a simple hello world tool that greets users with a customizable name.

Tool Usage

The helloWorld tool accepts an optional name parameter and returns a greeting message.

Parameters:

  • name: Name to greet (optional, defaults to "world")

Example Response:

Hello, world!

Installation

Global Installation (Recommended)

  1. Install globally via npm:

    npm install -g hello-world-mcp

  2. The hello-world-mcp command will be available system-wide

Local Installation

  1. Clone or download this repository

  2. Install dependencies:

    npm install

  3. Start the server:

    npm start

Usage

Starting the Server

npm start

MCP Configuration

For Global Installation

Add this to your MCP client configuration:

{
  "mcpServers": {
    "hello-world-mcp": {
      "command": "hello-world-mcp",
      "args": [],
      "env": {},
      "description": "Hello World MCP server with greeting tool"
    }
  }
}

For Local Installation

Add this to your MCP client configuration:

{
  "mcpServers": {
    "hello-world-mcp": {
      "command": "node",
      "args": ["index.js"],
      "cwd": "/path/to/hello-world-mcp",
      "env": {},
      "description": "Hello World MCP server with greeting tool"
    }
  }
}

Usage Examples

Hello World Tool

{
  "name": "helloWorld",
  "arguments": {
    "name": "Alice"
  }
}

Response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, Alice!"
    }
  ]
}

Default Greeting

{
  "name": "helloWorld",
  "arguments": {}
}

Response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, world!"
    }
  ]
}

Available Tools

Hello World Tool

helloWorld

A simple greeting tool that says "Hello, {name}" with default "world".

Parameters:

  • name: Name to greet (optional, defaults to "world")

Hello World Examples

Basic Greeting

{
  "name": "helloWorld",
  "arguments": {
    "name": "Alice"
  }
}

Response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, Alice!"
    }
  ]
}

Default Greeting

{
  "name": "helloWorld",
  "arguments": {}
}

Response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, world!"
    }
  ]
}

Response Format

The hello world tool returns a simple text response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, world!"
    }
  ]
}

Dependencies

  • @modelcontextprotocol/sdk: MCP SDK for server implementation

  • zod: Schema validation library

License

ISC

Available Tools

1 tool
helloWorldHello World ToolA

A simple hello world tool that greets the user

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoName to greet, defaults to 'world'world

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'greets the user' without stating whether this is a safe read-only operation, what the output looks like, or any side effects. The description is essentially a tautology of the tool's name and title, offering no extra behavioral context.

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, short sentence with no unnecessary words. It is front-loaded with the tool's purpose and earns its place, perfectly sized for a trivial hello-world tool.

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 simplicity and complete schema, the description adequately conveys the main function. However, there is no output schema, so the description could have mentioned the format of the greeting or any return value. For a greeting tool, this is implied but not explicitly stated, leaving a minor gap.

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 fully describes the only parameter (name) with a clear description and default value, so schema coverage is 100%. The description adds nothing beyond the schema, which is acceptable per the baseline guideline of scoring 3 when the schema covers parameters.

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

Purpose5/5

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

The description clearly states the tool greets the user with a specific verb ('greets') and resource ('the user'). There are no siblings to distinguish from, so the purpose is unambiguous.

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

Usage Guidelines3/5

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

Usage context is implied by the name and description ('hello world' is obviously used for greeting), but there is no explicit guidance on when to use this tool versus alternatives. Since no alternatives exist, the lack of comparison is acceptable, but the description still doesn't provide explicit context such as typical use cases.

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. 1 tool updatev1.0.0
    • First observedhelloWorld
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clear and unique, so an agent can unambiguously select it.

Naming Consistency5/5

The single tool uses a clear camelCase naming style. Consistency is trivially maintained with only one tool, and the name accurately reflects its functionality.

Tool Count5/5

The server is explicitly named 'hello-world-mcp' and its sole purpose is to greet the user. One tool is exactly the right scope, perfectly matching the server's narrow functionality.

Completeness5/5

The server's purpose is to provide a greeting, which the 'helloWorld' tool fully accomplishes. There are no missing operations for the defined domain, so the surface is complete.

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 Starter Server

    MatthewDailey
    A
    license
    C
    quality
    D
    maintenance
    This server provides a minimal template for creating AI assistant tools using the ModelContextProtocol, featuring a simple 'hello world' tool example and development setups for building custom MCP tools.
    1
    70
    14
    -

  • Hello World MCP Server

    AndresNinou
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    A simple demonstration MCP server that provides basic greeting functionality and server information. Enables users to generate hello messages and retrieve server details through tools and resources.
    -

  • Hello World MCP Server

    Auxin-io
    -
    license
    C
    quality
    Not graded
    maintenance
    A simple boilerplate MCP server that provides a basic greeting tool for demonstration purposes. Serves as a starting template for developers to quickly create and deploy custom MCP servers.
    1
    6
    -

  • Hello World MCP Server

    Auxin-io
    A
    license
    C
    quality
    D
    maintenance
    A simple MCP server that provides a basic greeting tool for saying hello with customizable names. Serves as a boilerplate template for developers to quickly create and deploy new MCP servers.
    1
    6
    MIT

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/niellevince/hello-world-mcp'

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