NestJS MCP Server Module

Created By
rekog-labsa year ago
A NestJS module to effortlessly create Model Context Protocol (MCP) servers for exposing AI tools, resources, and prompts.
Overview

What is MCP-Nest?

MCP-Nest is a NestJS module designed to simplify the creation of Model Context Protocol (MCP) servers, enabling developers to expose AI tools, resources, and prompts seamlessly from their NestJS applications.

How to use MCP-Nest?

To use MCP-Nest, install the module via npm, import it into your NestJS application, and define your tools and resources using decorators provided by the module.

Key features of MCP-Nest?

  • 🚀 Support for multiple transport types including Streamable HTTP, HTTP+SSE, and STDIO.
  • 🔍 Automatic discovery and registration of tools, resources, and prompts.
  • 💯 Zod-based validation for tool calls.
  • 📊 Progress notifications for long-running operations.
  • 🔒 Guard-based authentication for securing endpoints.

Use cases of MCP-Nest?

  1. Building enterprise-ready AI tool servers.
  2. Exposing various AI resources and prompts for client applications.
  3. Implementing real-time updates and progress notifications in applications.

FAQ from MCP-Nest?

  • Can MCP-Nest be used with any NestJS application?

Yes! MCP-Nest is designed to integrate seamlessly with any NestJS application.

  • Is MCP-Nest free to use?

Yes! MCP-Nest is open-source and free to use under the MIT license.

  • What transport types does MCP-Nest support?

MCP-Nest supports Streamable HTTP, HTTP+SSE, and STDIO transport types.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rekog-labs
Star
160
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago