Skip to main content
Glama
ns-personal

MCP Server Boilerplate

by ns-personal
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

MCP Server Boilerplate

A basic Model Context Protocol (MCP) server implementation that can be used as a starting point for building MCP-compatible applications.

Features

  • Basic MCP server setup with TypeScript

  • Example function implementation

  • Graceful shutdown handling

  • Development and production build configurations

Related MCP server: MCP TypeScript Template

Prerequisites

  • Node.js (v14 or higher)

  • npm or yarn

Installation

npm install

Development

To run the server in development mode with hot-reload:

npm run dev

Building for Production

To build the project:

npm run build

To start the production server:

npm start

Project Structure

├── src/
│   └── index.ts    # Main server implementation
├── package.json    # Project dependencies and scripts
├── tsconfig.json  # TypeScript configuration
└── README.md      # This file

Adding New MCP Functions

To add new functions to the server:

  1. Define a new function schema using Zod

  2. Create a function implementation following the MCPFunction interface

  3. Add the function to the server configuration

Example:

const myNewFunction: MCPFunction = {
  name: 'my_new_function',
  description: 'Description of what the function does',
  parameters: z.object({
    // Define your parameters here
  }),
  handler: async (params) => {
    // Implement your function logic here
    return {
      // Return your response here
    };
  }
};

License

ISC

Available Tools

1 tool
echoD
ParametersJSON Schema
NameRequiredDescriptionDefault
messageYes

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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 observedecho
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.7/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The tool 'echo' stands alone with no ambiguity in its purpose relative to other tools in the set.

Naming Consistency5/5

Since there is only one tool named 'echo', there is no inconsistency in naming patterns to evaluate. The tool name follows a simple, single-word convention, and with no other tools, it cannot be inconsistent.

Tool Count2/5

A single tool named 'echo' with no description suggests a minimal or trivial server, which may be insufficient for most practical purposes. While it could be appropriate for a very narrow scope, it likely feels thin and underdeveloped for typical MCP server use cases.

Completeness1/5

With only one tool and no description provided, it is impossible to assess coverage of any domain. The tool set is severely incomplete, as there are no other tools to form a coherent surface, and the lack of description makes it unclear what functionality is even intended.

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 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.
    54
    MIT

  • MCP TypeScript Template

    mintedmaterial
    A
    license
    Not graded
    quality
    D
    maintenance
    A production-grade TypeScript template for building Model Context Protocol (MCP) servers with declarative tools/resources, authentication, storage abstraction, and support for both local and edge deployment. Provides example echo tools and resources to demonstrate MCP server development patterns.
    286
    Apache 2.0

  • Starter MCP Server

    YunYouJun
    A
    license
    B
    quality
    D
    maintenance
    A template/boilerplate project for building Model Context Protocol (MCP) servers with TypeScript. Provides a starting point with configuration examples, development tools, and debugging setup.
    2
    1
    MIT

  • 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.
    88
    -

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/ns-personal/echo-map'

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