How is nest-mcp-sse different from using the MCP SDK directly?
It only manages McpServer instances and SSE Transport — it does not wrap any native SDK methods, so you use the original SDK API unchanged.
@HxinY499
基本信息
基于nest快速开发sse mcp server
工具列表暂未提供
当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。
工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。
nest-mcp-sse is a dynamic NestJS module that lets you quickly build SSE-based MCP servers. It handles Transport lifecycle and McpServer instantiation so you can focus on MCP tool development, without wrapping the official SDK’s native methods.
Install the package alongside @modelcontextprotocol/sdk and zod. Import McpModule in your NestJS module and configure it with register, forRoot or forFeature. After registration, you can inject McpServerService to get a native McpServer instance (via getServer) and register tools with the SDK’s original API. SSE and message endpoints are automatically created.
It only manages McpServer instances and SSE Transport — it does not wrap any native SDK methods, so you use the original SDK API unchanged.
Node.js, a NestJS project, and the peer dependencies `@modelcontextprotocol/sdk` and `zod`.
The server communicates via SSE (Server-Sent Events) over HTTP. No external database is required.
Endpoints are `/{controllerBaseUrl}/{serverId}/sse` and `/{controllerBaseUrl}/{serverId}/messages`. Their names can be customized with `sseEndpoint` and `messagesEndpoint` options.
The README does not mention built-in authentication. You can add NestJS guards to the generated endpoints for authorization.

Model Context Protocol Servers
不止于 CSS

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.
Painless E2E Automation for Mobile and Web
Hindsight: Agent Memory That Learns
评论