server▌

Goal: Keep route.ts minimal. Put logic + Zod schemas in lib/* so both the MCP handler and server actions share a single source of truth.

You are guiding a developer through designing and building an MCP server that works seamlessly with Claude. MCP servers come in many forms — picking the wrong shape early causes painful rewrites later. Your first job is discovery, not code.

Server management principles for production operations. Learn to THINK, not memorize commands.

Complete reference for running Agentica SDK with a local Claude proxy. This enables Python agents to use Claude CLI as their inference backend.

Enrich an existing MCP server's tools with interactive UIs using the MCP Apps SDK (@modelcontextprotocol/ext-apps).

Deploy remote MCP servers on Cloudflare Workers with TypeScript, OAuth, and Durable Objects. \n \n Supports SSE and HTTP Streamable transports with automatic WebSocket hibernation for stateful sessions; choose from five auth templates (no-auth, bearer, GitHub/Google OAuth, enterprise SSO) \n Base path configuration is critical—server and client URLs must match exactly (e.g., serveSSE(\"/sse\") requires client URL https://worker.dev/sse , not https://worker.dev ) \n Includes 24 documented error s

Framework for production server operations covering process management, monitoring, logging, and scaling decisions. \n \n Covers seven core operational areas: process management tool selection (PM2, systemd, Docker, Kubernetes), monitoring strategy with severity-based alerting, and structured log rotation practices \n Provides decision matrices for scaling (vertical vs. horizontal vs. auto-scaling), health check depth, and troubleshooting priority order \n Emphasizes principles over commands: au

Build MCP servers with Spring AI using declarative tools, prompt templates, and native Spring integration patterns. \n \n Exposes Spring components as AI-callable tools via @Tool annotation, with parameter documentation through @ToolParam for AI model understanding \n Supports three transport modes (stdio, HTTP, SSE) with built-in Spring Security integration for role-based access control and audit logging \n Includes reusable prompt templates using @PromptTemplate , dynamic tool registration, mu

Production-ready Express.js servers with routing, middleware, authentication, and database integration. \n \n Covers core Express patterns including middleware chains, RESTful routing with CRUD operations, and error handling middleware \n Supports authentication via JWT, database integration with PostgreSQL and Sequelize, and environment-based configuration \n Includes best practices for input validation, async/await patterns, rate limiting, and HTTPS in production \n Reference guides provided f

Provide comprehensive guidance for choosing between Server Components and Client Components in Next.js App Router, including cookie/header access, searchParams handling, pathname routing, and React's 'use' API for promise unwrapping.