simply -ts

Simply MCP TS provides a type-safe framework for building MCP servers using pure TypeScript interfaces. You define your server’s capabilities, tools, prompts, and resources with strong type guarantees, and Simply MCP automatically derives the MCP protocol schemas, transport bindings, and UI hooks. The README demonstrates a two-pattern approach: a const-based pattern that emphasizes zero boilerplate and type inference, and a class-based pattern for scenarios requiring shared state or more complex initialization. With the included transport options (stdio, HTTP with sessions, and stateless HTTP for serverless setups) you can pick the right runtime behavior for your deployment. The framework also integrates with the official MCP SDK under the hood, providing features like hot-reload, UI adapters, and OAuth 2.1 authentication configured through your TypeScript interfaces. In practice, you define your tools as TypeScript interfaces, export implementations, and run the server using the MCP runner (e.g., npx simply-mcp run server.ts). The tooling supports rich parameter types, nested objects, arrays, unions, and descriptive JSDoc comments, all reflected in the generated protocol schemas and client-facing APIs.

Prerequisites:

• Node.js >= 20.0.0
• npm or pnpm

Installation steps:

# Install the Simply MCP package in your project
npm install simply-mcp

Optional dependencies are lazy-loaded and only required when you use them:

• HTTP transport: express, cors
• Watch mode: chokidar
• Bundling: esbuild
• Minification: terser, html-minifier-terser, cssnano
• Client rendering: @remote-dom/core, @remote-dom/react, react, react-dom

# If you want to try running a sample server directly via npx (as shown in the README)
npx simply-mcp run server.ts

Create your server file (e.g., server.ts) following the const-pattern or class-pattern examples in the README, then start the server with the MCP runner as shown above.

Tips and common considerations:

• The TypeScript interfaces drive the entire MCP protocol generation. Prefer the const pattern for minimal boilerplate and automatic type inference.
• If you encounter TypeScript type errors, switch to ToolHelper-based tooling or refine your interfaces to match expected parameter shapes.
• Transport selection affects how state is managed: use STDIO for CLI workflows and HTTP transports for multi-user sessions with SSE support.
• Enable hot-reload during development to see schema updates and client API changes in real-time.
• Review the API_REFERENCE.md and protocol guides in the docs directory for advanced features like sampling, elicitation, roots, subscriptions, and UI adapters.