Skip to main content
Glama
enesjakozh
coinselor

MCP Server Starter

by coinselor
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

MCP Server Starter

A production-ready starter template for building Model Context Protocol (MCP) servers with TypeScript.

🚀 Quick Start

  1. Clone the repository

  2. Install dependencies:

    bun install

Related MCP server: MCP Server Starter

✨ Key Features

  • Bun for fast testing and development

  • Biome for linting and formatting

  • Automated version management with standard-version

  • Clean, maintainable project structure

📂 Project Structure

mcp-starter/
├── src/
│   ├── tools/          # MCP tools implementation
│   ├── utils/          # Shared utilities
│   ├── main.ts         # Server entry point
│   └── types.ts        # Shared type definitions
├── tests/              # Test files
├── biome.json          # Linting configuration
├── tsconfig.json       # TypeScript configuration
└── package.json        # Project dependencies

⚙️ Configuration

Creating New Tools

The project includes a script to help create new MCP tools:

bun run scripts/create-tool.ts <tool-name>

This will:

  1. Create a new tool directory under src/tools/<tool-name>

  2. Generate the basic tool structure including:

    • index.ts (main implementation)

    • schema.ts (JSON schema for tool parameters)

    • test.ts (test file)

  3. Update the tools index file to export the new tool

Example:

bun run scripts/create-tool.ts weather

🛠️ Development

  • Run tests: bun test

  • Format code: bun run format

  • Lint code: bun run lint

  • Build project: bun run build

To add your development MCP server to Claude Desktop:

  1. Build the project:

    bun run build

  2. Add to your Claude Desktop config:

    // You only need the argument if you need to pass arguments to your server
{
  "mcpServers": {
    "your-server-name": {
      "command": "node",
      "args": ["/path/to/your/project/dist/main.js", "some_argument"]
    }
  }
}

📜 Version Management

This project uses standard-version for automated version management. Run bun run release to create a new version.

Commit Message Format

  • feat: New feature (bumps minor version)

  • fix: Bug fix (bumps patch version)

  • BREAKING CHANGE: Breaking change (bumps major version)

📦 Publishing to npm

  1. Ensure you're logged in to npm:

    npm login

  2. Build the project:

    bun run build

  3. Publish the package:

    npm publish

Remember to update the version number using bun run release before publishing new versions.

Installing from npm (after publishing)

Add to your Claude Desktop config:

// You only need the argument if you need to pass arguments to your server
{
  "mcpServers": {
    "your-server-name": {
      "command": "npx",
      "args": ["-y", "your-package-name", "some_argument"]
    }
  }
}

Available Tools

1 tool
hello_toolD

Hello tool

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the person to greet

TDQS

D1.9/5.0
Behavior1/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. 'Hello tool' gives no information about what the tool actually does behaviorally - whether it's a read operation, a write operation, what permissions might be needed, what the response looks like, or any side effects. This is completely inadequate for a tool with any functionality.

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

Conciseness2/5

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

While technically concise with only two words, this represents under-specification rather than effective conciseness. The description fails to communicate essential information about the tool's purpose and behavior. Every word should earn its place, but here the words don't provide meaningful value beyond the tool name itself.

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?

Given a tool with one parameter and no annotations or output schema, the description 'Hello tool' is completely inadequate. It doesn't explain what the tool does, when to use it, what behavior to expect, or what the output might be. For even a simple greeting tool, this description leaves the agent guessing about fundamental aspects of the tool's functionality.

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 schema clearly documenting that the single required parameter 'name' is 'The name of the person to greet'. The description adds no parameter information beyond what's in the schema. With high schema coverage, the baseline is 3 even when the description provides no additional parameter semantics.

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

Purpose2/5

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

The description 'Hello tool' is a tautology that merely restates the tool name without specifying what it actually does. While it hints at greeting functionality through the word 'Hello', it doesn't clearly state the verb+resource combination (e.g., 'greets a person by name'). The description is vague about the specific action performed.

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?

No guidance is provided about when to use this tool. The description doesn't mention any context, prerequisites, or alternatives. With no sibling tools, the bar is lower, but the description still fails to provide any usage context beyond the minimal implication from the name and single parameter.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.3/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The single tool's purpose is clearly distinct by default, eliminating any risk of misselection.

Naming Consistency5/5

The tool name 'hello_tool' follows a consistent snake_case pattern, and with only one tool, there is no inconsistency in naming conventions. The naming is straightforward and predictable within this minimal set.

Tool Count2/5

A single tool is generally too few for a server's purpose, as it suggests a very limited or trivial scope that may not support meaningful agent workflows. This is borderline for appropriateness, leaning toward insufficient coverage for typical MCP server use cases.

Completeness1/5

With only one tool named 'hello_tool', the server's domain is unclear, making it impossible to assess coverage meaningfully. There are likely significant gaps for any inferred purpose, as a single tool cannot provide CRUD/lifecycle operations or a coherent workflow, leading to severe incompleteness.

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

Appeared in Searches

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/coinselor/mcp-zenon'

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