Skip to main content
Glama
vidyasagarr7

mcp-ts-template

by vidyasagarr7
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

mcp-ts-template

Production-ready Model Context Protocol (MCP) server template in TypeScript, built on the official @modelcontextprotocol/sdk. Ships an example tool, resource, and prompt.

Use this template

gh repo create my-mcp --template vidyasagarr7/mcp-ts-template

Related MCP server: MCP Server Starter

Layout

src/
  server.ts        # stdio entry point (transport wiring only)
  index.ts         # createServer(): registers tools/resources/prompts
  core/tools.ts    # pure domain logic (testable, no MCP concerns)
  version.ts
tests/             # vitest specs

Golden rule: transport in server.ts, registration in index.ts, logic in core/.

Develop

npm install
npm run dev            # run server from source over stdio
npm test               # vitest
npm run typecheck
npm run build
npm run inspect        # launch MCP Inspector against the built server

Try the server by hand

npm run build
# Initialize handshake over stdio:
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}' | node dist/server.js

Register a new tool

  1. Add pure logic to src/core/tools.ts.

  2. Add a unit test in tests/.

  3. Register it in src/index.ts via server.registerTool(...) with a zod input schema.

Connect from a client

Point any MCP client (Claude Desktop, MCP Inspector, etc.) at the built binary:

{
  "mcpServers": {
    "my-mcp": { "command": "node", "args": ["/abs/path/dist/server.js"] }
  }
}

Make it yours (rename checklist)

  • package.json: name, description, bin key, repository, keywords

  • src/index.ts: new McpServer({ name: ... })

  • Replace the example add tool / greeting resource / summarize prompt with your own

  • Keep transport in server.ts, registration in index.ts, logic in core/

License

MIT

Available Tools

1 tool
addAddA

Add two numbers

ParametersJSON Schema
NameRequiredDescriptionDefault
aYesfirst addend
bYessecond addend

TDQS

A4.3/5.0
Behavior4/5

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

Without annotations, the description carries full burden. It accurately describes a pure function with no side effects. However, it does not mention that the result is a number or potential overflow, but the schema implies numeric return.

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 sentence of four words, perfectly concise with no wasted words. It front-loads the action and object.

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

Completeness5/5

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

For a simple arithmetic tool with two clear number parameters and no output schema, the description is complete. It covers purpose and behavior adequately.

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 coverage is 100% with descriptions 'first addend' and 'second addend'. The description adds no additional meaning beyond these, so a baseline 3 is appropriate.

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 'Add two numbers' clearly states the verb (Add) and resource (two numbers), leaving no ambiguity about the tool's purpose. It is specific and need not differentiate from siblings as none exist.

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

Usage Guidelines4/5

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

The description doesn't provide explicit when-to-use or alternative guidance, but given the tool's simplicity and absence of siblings, the usage context is obvious. It misses an opportunity to mention that this is for simple numeric addition only.

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

TDQS

A4.3/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and unambiguous.

Naming Consistency5/5

With a single tool, naming is trivially consistent. The name 'add' follows a simple verb pattern appropriate for its function.

Tool Count4/5

As a template server, a single tool is slightly minimal but acceptable. It provides a basic starting point for extension.

Completeness3/5

Within the narrow domain of adding two numbers, the tool is complete. However, for a broader utility server, it lacks other arithmetic operations like subtract, multiply, or divide.

Maintenance

ActivityMaintained
ResponsivenessSyncing

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

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/vidyasagarr7/mcp-ts-template'

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