MCP-Nest MCP — Use Cases, Install & Live Demo

Why use it

Key features

Decorator-based: @Tool, @Resource, @Prompt wrap normal Nest methods
Multi-transport: stdio + HTTP+SSE + Streamable HTTP in one server
Auth via standard Nest guards (JWT, Keycloak, Auth0)
Zod input validation built in

Live Demo

What it looks like in practice

nest.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "nest": {
      "command": "npx",
      "args": [
        "-y",
        "MCP-Nest"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "nest": {
      "command": "npx",
      "args": [
        "-y",
        "MCP-Nest"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "nest": {
      "command": "npx",
      "args": [
        "-y",
        "MCP-Nest"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "nest": {
      "command": "npx",
      "args": [
        "-y",
        "MCP-Nest"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "nest",
      "command": "npx",
      "args": [
        "-y",
        "MCP-Nest"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "nest": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "MCP-Nest"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add nest -- npx -y MCP-Nest

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use MCP-Nest

Expose your existing NestJS backend as an MCP

👤 NestJS teams whose agents need to call internal APIs ⏱ ~45 min intermediate

When to use: You don't want to rewrite service logic in Python or TS MCP SDK — reuse what's already tested.

Prerequisites

NestJS 10+ app — Your existing project
Install @rekog/mcp-nest — npm i @rekog/mcp-nest

Flow

Register the module

Add McpModule.forRoot({name: 'acme', version: '1.0'}) to app.module.ts.✓ Copied

→ App starts; /mcp endpoint present
Decorate a service method as a tool

In TicketsService, decorate searchTickets with @Tool({name:'search_tickets', description:'...'}) and a Zod schema. Existing auth guards still apply.✓ Copied

→ Tool shows in Claude's tool list
Hook up auth

Apply the existing JwtAuthGuard on the MCP controller so agents need a valid bearer token.✓ Copied

→ Unauth'd calls return 401

Outcome: Your agents consume your real backend — same validation, same auth, no service duplication.

Pitfalls

Mixing user-scoped and service-scoped tools creates auth confusion — Split into two MCP modules: one with user JWT, one with service token

Build an interactive tool that asks the user for input mid-call

👤 Nest developers building advanced agent flows ⏱ ~30 min advanced

When to use: Your tool needs confirmation or a secret that the agent shouldn't have by default.

Flow

Use the elicitation API inside a tool

In the delete_account tool, before deleting, elicit a typed confirmation from the user (the real human, not the agent).✓ Copied

→ Agent prompts the user in chat; proceeds only on confirmation

Outcome: Irreversible actions gated behind human input even through an agent.

Serve dynamic Nest data as MCP resources

👤 Teams that want agents to read fresh data, not stale snapshots ⏱ ~35 min advanced

When to use: Agents need to see live status (build, deploy, ticket queue) as context, not via a tool call.

Flow

Declare a resource template

Create a @Resource('ticket://{id}') that returns the ticket JSON by id.✓ Copied

→ Agent can reference ticket://123 and get live content
Subscribe to updates

Emit updates when the ticket changes so subscribers see fresh state without polling✓ Copied

→ MCP push notifications to subscribed clients

Outcome: Live context instead of snapshots — the agent sees what the user sees.

Combinations

Pair with other MCPs for X10 leverage

nest + golf

Python shop + TS shop both build MCPs the same framework-first way

Port our Python Golf MCP features to the Nest team's MCP-Nest server — compare ergonomics.✓ Copied

nest + mcptools

Verify tool schemas during CI before deploy

In CI, spin up the Nest MCP and run mcp tools to assert expected tool list.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
@Tool({...}) decorator	method args validated via Zod schema	Mark any Nest service method as an MCP tool	standard Nest method cost
@Resource({...}) decorator	URI template params	Expose dynamic/static resources	standard Nest cost
@Prompt({...}) decorator	prompt vars	Ship prompts as versioned code	0

Cost & Limits

What this costs to run

API quota: Depends on your services
Tokens per call: Depends on tool output
Monetary: Free, MIT
Tip: Add response size guards on tools that return lists — an unbounded list of tickets will blow token budgets fast

Security

Permissions, secrets, blast radius

Credential storage: Standard Nest config; use @nestjs/config + secret managers

Data egress: Wherever your Nest services go

Troubleshooting

Common errors and fixes

Tool not appearing in Claude

Ensure the class is registered in a module provider and the decorator import is from @rekog/mcp-nest not a stale copy

Verify: curl http://localhost:3000/mcp tools/list

Zod validation errors at runtime

Your schema doesn't match actual inputs the agent sends — tighten descriptions so the model fills the right fields

SSE connection drops every 30s

Upstream proxy timeout; set keepalive in nginx to 60s+ or use Streamable HTTP transport instead

Alternatives

MCP-Nest vs others

Alternative	When to use it instead	Tradeoff
TS MCP SDK (official)	You don't use NestJS and want the raw SDK	No DI, no guards, you wire everything
Golf	Python backend	Different language; similar framework ambitions
FastMCP	Python, simpler than Golf	Less enterprise tooling

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills