Sanketshinde3001 MCP

MCPAI代理

提供方 sanketshinde3001 · 包名 @modelcontextprotocol/inspector

AI代理 stdio · 本地进程 无需鉴权 社区 / 第三方 VS Code
查看接入方式

一个展示如何使用TypeScript和@modelcontextprotocol/sdk创建和交互MCP服务器与客户端的项目,适用于开发工具链集成和自动化测试场景。

一句话选型结论

按资料字段整理

Sanketshinde3001 MCP 属于AI代理类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 VS Code,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 1 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量1暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

MCP协议TypeScript本地部署TypeScript开发工具链集成自动化测试

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
npx @modelcontextprotocol/inspector node /path/to/my-mcp-greeter-server/build/index.js

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 1 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 1 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 VS Code,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 VS Code 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Sanketshinde3001 MCP当前 1 stdio · 本地进程 本地部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方sanketshinde3001上游标注的维护方 sanketshinde3001
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@modelcontextprotocol/inspector · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

7.4 KB
来自项目仓库与上游目录的原文,未做删改

MCP Server and Client Example (TypeScript)

This project demonstrates the creation and interaction of a simple Model Context Protocol (MCP) server and a standalone MCP client using TypeScript and the @modelcontextprotocol/sdk.

The setup includes:
1. my-mcp-greeter-server: An MCP server that provides greeting-related tools, resources, and prompts.
2. my-mcp-client-script: A simple command-line client script that launches the server, connects to it, and interacts with its capabilities programmatically.

Communication between the client and server in this example uses the stdio (standard input/output) transport mechanism.

Overview of the Process Followed

This project was built following these main phases:

  1. Server Development: Creating the MCP service provider.
  2. Client Development: Creating a script to consume the server's services.
  3. Testing & Interaction: Running the client script, which launches the server and demonstrates communication.
  4. (Optional) Integration: Discussing how to integrate the server with existing MCP clients like VS Code extensions.

Prerequisites

Before you begin, ensure you have the following installed:
* Node.js (v16 or higher recommended)
* npm (usually included with Node.js)
* A text editor or IDE (like VS Code)
* npx (usually included with npm) - useful for testing with MCP Inspector.

Phase 1: Building the MCP Server (my-mcp-greeter-server)

  1. Project Setup:

    • Created the directory my-mcp-greeter-server.
    • Initialized an npm project: npm init -y.
    • Installed necessary dependencies: npm install @modelcontextprotocol/sdk zod.
    • Installed development dependencies: npm install -D typescript @types/node.
    • Initialized TypeScript configuration: npx tsc --init.
    • Configured tsconfig.json (setting "module": "Node16", "target": "ES2022", "outDir": "./build", "rootDir": "./src", etc.).
    • Updated package.json to include "type": "module" and added build/start scripts.
    • Created the source file src/index.ts.
  2. Server Implementation (src/index.ts):

    • Imported required modules (McpServer, StdioServerTransport, z).
    • Defined constants for server name and version.
    • Instantiated McpServer, passing the name, version, and declaring its capabilities (tools, resources, prompts).
    • Defined a Tool (greet): Used server.tool() to create a function callable by clients. Included a description, defined input parameters with Zod (name, politeness), and implemented the handler to return a personalized greeting string.
    • Defined a Resource (server-info): Used server.resource() to expose static data. Provided a unique URI (info://greeter/about) and implemented the handler to return the server's name and version.
    • Defined a Prompt (suggest-greeting): Used server.prompt() to create a reusable interaction template. Included a description and implemented the handler to return a predefined set of user/assistant messages to guide an LLM interaction.
    • Used Stdio Transport: Instantiated StdioServerTransport as the communication method.
    • Connected: Called await server.connect(transport) to make the server ready.
    • Logging: Added console.error statements for visibility during execution, especially important for stdio transport where stdout is used for protocol messages.
    • Kept Alive: Ensured the Node.js process didn't exit immediately after connection.
  3. Building & Fixing:

    • Ran npm run build to compile TypeScript to JavaScript in the build directory.
    • Fixed a TypeScript error related to accessing server version directly, opting to use predefined constants instead.

Phase 2: Building the MCP Client Script (my-mcp-client-script)

  1. Project Setup:

    • Created a separate directory my-mcp-client-script.
    • Initialized an npm project: npm init -y.
    • Installed necessary dependencies: npm install @modelcontextprotocol/sdk.
    • Installed development dependencies: npm install -D typescript @types/node.
    • Initialized and configured tsconfig.json similarly to the server project.
    • Updated package.json with "type": "module" and build/start scripts.
    • Created the source file src/client-script.ts.
  2. Client Implementation (src/client-script.ts):

    • Imported required modules (Client, StdioClientTransport, path, url).
    • Determined Server Path: Calculated the path to the server's compiled index.js file (relative or absolute).
    • Configured Stdio Transport: Instantiated StdioClientTransport, providing the command (node) and args (the path to the server script). This configuration is key, as the client transport launches the server process.
    • Instantiated Client: Created a Client instance, giving it an identity and declaring its intent to use tools and resources.
    • Connected: Called await client.connect(transport), which launched the server process and established the MCP connection over its stdio streams.
    • Interacted with Server:
      • Called the greet tool using await client.callTool().
      • Read the server-info resource using await client.readResource().
      • Fetched the suggest-greeting prompt using await client.getPrompt().
    • Logged Results: Used console.log to display the responses received from the server.
    • Closed Connection: Used await client.close() in a finally block to cleanly shut down the connection and terminate the server process.

Phase 3: Building and Running

  1. Build Both Projects:

    • cd my-mcp-greeter-server && npm run build
    • cd ../my-mcp-client-script && npm run build
  2. Run the Client:

    • cd my-mcp-client-script
    • npm run start (or node build/client-script.js)
    • Observed the interleaved output from both the client (console.log) and the server (console.error), confirming successful communication and execution of tools/resources/prompts.

Explanation of Roles

  • The Server (GreeterServer):

    • Provides Services: Exposes specific capabilities (greeting tool, server info, prompt template).
    • Passive Listener (in stdio): Waits for a client to connect via its standard streams.
    • Executes Logic: Runs the code associated with a tool/resource/prompt when requested by the client.
    • Sends Results: Formats results according to MCP specs and sends them back to the client.
  • The Client (client-script.ts):

    • Consumes Services: Uses the capabilities offered by the server.
    • Initiator (in stdio): Launches the server process and establishes the connection.
    • Sends Requests: Decides which tool to call, resource to read, or prompt to get, and sends the appropriate MCP request.
    • Receives Results: Processes the responses sent back by the server.
    • Controls Flow: Manages the sequence of interactions and decides when to close the connection.

Testing the Server Interactively

While the client script tests the programmatic interaction, you can test the server's capabilities individually using the MCP Inspector:

# Make sure the server is NOT already running
# Replace /path/to/... with the actual absolute path
npx @modelcontextprotocol/inspector node /path/to/my-mcp-greeter-server/build/index.js

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Sanketshinde3001 MCP 怎么安装?

在客户端按下面的安装命令接入:npx @modelcontextprotocol/inspector node /path/to/my-mcp-greeter-server/build/index.js。对应的包名是 @modelcontextprotocol/inspector。装完在客户端配置里引用同一个包或端点。

Sanketshinde3001 MCP 怎么在 VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Sanketshinde3001 MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Sanketshinde3001 MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Sanketshinde3001 MCP 支持哪些客户端?

资料标注支持 VS Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Sanketshinde3001 MCP 能提供哪些能力?

资料显示约 1 个工具;能力标签包括 自动化测试、TypeScript、VS Code、TypeScript开发。具体工具清单以官方文档为准。

Sanketshinde3001 MCP 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

Sanketshinde3001 MCP 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。