Typescript Mcp Server Generator

1---2name: typescript-mcp-server-generator3description: 'Generate a complete MCP server project in TypeScript with tools, resources, and proper configuration'4---5 6# Generate TypeScript MCP Server7 8Create a complete Model Context Protocol (MCP) server in TypeScript with the following specifications:9 10## Requirements11 121. **Project Structure**: Create a new TypeScript/Node.js project with proper directory structure132. **NPM Packages**: Include @modelcontextprotocol/sdk, zod@3, and either express (for HTTP) or stdio support143. **TypeScript Configuration**: Proper tsconfig.json with ES modules support154. **Server Type**: Choose between HTTP (with Streamable HTTP transport) or stdio-based server165. **Tools**: Create at least one useful tool with proper schema validation176. **Error Handling**: Include comprehensive error handling and validation18 19## Implementation Details20 21### Project Setup22- Initialize with `npm init` and create package.json23- Install dependencies: `@modelcontextprotocol/sdk`, `zod@3`, and transport-specific packages24- Configure TypeScript with ES modules: `"type": "module"` in package.json25- Add dev dependencies: `tsx` or `ts-node` for development26- Create proper .gitignore file27 28### Server Configuration29- Use `McpServer` class for high-level implementation30- Set server name and version31- Choose appropriate transport (StreamableHTTPServerTransport or StdioServerTransport)32- For HTTP: set up Express with proper middleware and error handling33- For stdio: use StdioServerTransport directly34 35### Tool Implementation36- Use `registerTool()` method with descriptive names37- Define schemas using zod for input and output validation38- Provide clear `title` and `description` fields39- Return both `content` and `structuredContent` in results40- Implement proper error handling with try-catch blocks41- Support async operations where appropriate42 43### Resource/Prompt Setup (Optional)44- Add resources using `registerResource()` with ResourceTemplate for dynamic URIs45- Add prompts using `registerPrompt()` with argument schemas46- Consider adding completion support for better UX47 48### Code Quality49- Use TypeScript for type safety50- Follow async/await patterns consistently51- Implement proper cleanup on transport close events52- Use environment variables for configuration53- Add inline comments for complex logic54- Structure code with clear separation of concerns55 56## Example Tool Types to Consider57- Data processing and transformation58- External API integrations59- File system operations (read, search, analyze)60- Database queries61- Text analysis or summarization (with sampling)62- System information retrieval63 64## Configuration Options65- **For HTTP Servers**: 66  - Port configuration via environment variables67  - CORS setup for browser clients68  - Session management (stateless vs stateful)69  - DNS rebinding protection for local servers70  71- **For stdio Servers**:72  - Proper stdin/stdout handling73  - Environment-based configuration74  - Process lifecycle management75 76## Testing Guidance77- Explain how to run the server (`npm start` or `npx tsx server.ts`)78- Provide MCP Inspector command: `npx @modelcontextprotocol/inspector`79- For HTTP servers, include connection URL: `http://localhost:PORT/mcp`80- Include example tool invocations81- Add troubleshooting tips for common issues82 83## Additional Features to Consider84- Sampling support for LLM-powered tools85- User input elicitation for interactive workflows86- Dynamic tool registration with enable/disable capabilities87- Notification debouncing for bulk updates88- Resource links for efficient data references89 90Generate a complete, production-ready MCP server with comprehensive documentation, type safety, and error handling.