F
licenseNot graded
qualityD
maintenanceA demonstration implementation of the Model Context Protocol server that facilitates communication between AI models and external tools while maintaining context awareness.
-
MCP TypeScript Simple Template
by ChenReuven
MCP TypeScript 简单模板
一个用于构建模型上下文协议 (MCP) 服务器的简单 TypeScript 模板。该项目为创建可与 AI 系统集成的自定义 MCP 工具奠定了基础。
概述
此模板实现了一个基本的 MCP 服务器，其中包含一个示例 BMI 计算器工具。它演示了如何：
使用 TypeScript 设置 MCP 服务器
使用 Zod 定义并实现具有输入验证的 MCP 工具
将服务器连接到标准 I/O 进行通信
Related MCP server: MCP Server Python Template
先决条件
Node.js（建议使用 v20 或更高版本）
npm 或 yarn
安装
克隆此存储库
安装依赖项：
npm install项目结构
index.ts- 带有示例工具的主服务器实现package.json- 项目依赖项和脚本tsconfig.json- TypeScript 配置
用法
构建和运行
构建并启动服务器：
npm start这将编译 TypeScript 代码并启动 MCP 服务器。
发展
对于开发，您可以：
修改
index.ts以添加您自己的工具运行build命令进行编译：
npm run build创建自定义工具
要创建新工具，请在index.ts中遵循以下模式：
server.tool(
"your-tool-name",
{
// Define input schema using Zod
paramName: z.string(),
// Add more parameters as needed
},
async ({ paramName }) => ({
content: [{
type: "text",
text: "Your tool's response"
}]
})
);依赖项
@modelcontextprotocol/sdk- 核心 MCP SDKzod- 模式验证dotenv环境变量管理typescript- TypeScript 编译器
执照
国际学习中心
贡献
欢迎贡献代码！欢迎提交 Pull 请求。
Available Tools
2 toolscalculate-bmiD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| heightM | Yes | ||
| weightKg | Yes |
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.
echoD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes |
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.
2 tool updates
v1.0.0- First observed
calculate-bmi - First observed
echo
TDQS
D1.5/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: calculate_bmi is for health-related calculations, while echo is for text repetition. There is no overlap or ambiguity between them, making it easy for an agent to choose the right tool.
Naming Consistency2/5
The naming is inconsistent: calculate_bmi uses kebab-case, while echo uses lowercase without a clear pattern. There is no consistent verb_noun convention, and the styles are mixed, though the names are still readable.
Tool Count2/5
With only 2 tools, the server feels too thin for a general-purpose template. It lacks depth and variety, suggesting an incomplete or minimal implementation that doesn't fully cover a meaningful domain.
Completeness1/5
The server is severely incomplete; it only offers two unrelated tools with no descriptions, making it impossible to assess domain coverage. There are obvious gaps, and it doesn't support any coherent workflow or lifecycle.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceA streamlined foundation for building Model Context Protocol servers in Python, designed to make AI-assisted development of MCP tools easier and more efficient.12MIT
- AlicenseDqualityDmaintenanceA foundation for building custom local Model Context Protocol (MCP) servers that provide tools accessible to AI assistants like Cursor or Claude Desktop.137MIT
- -licenseNot gradedqualityDmaintenanceA standardized foundation for building Model Context Protocol servers that integrate with VS Code, using Python with stdio transport for seamless AI tool integration.-