github/awesome-copilot/skills/typescript-mcp-server-generator/SKILL.md
typescript-mcp-server-generator
Generate a complete MCP server project in TypeScript with tools, resources, and proper configuration
- Source repository stars
- 37,126
- Declared platforms
- 0
- Static risk flags
- 1
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Create a complete Model Context Protocol (MCP) server in TypeScript with the following specifications:
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/github/awesome-copilot --skill "skills/typescript-mcp-server-generator"Inspect the Agent Skill "typescript-mcp-server-generator" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/typescript-mcp-server-generator/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Implementation Details
Initialize with npm init and create package.json
Initialize with npm init and create package.jsonInstall dependencies: @modelcontextprotocol/sdk, zod@3, and transport-specific packagesConfigure TypeScript with ES modules: "type": "module" in package.json - 02
Project Setup
Initialize with npm init and create package.json
Initialize with npm init and create package.jsonInstall dependencies: @modelcontextprotocol/sdk, zod@3, and transport-specific packagesConfigure TypeScript with ES modules: "type": "module" in package.json - 03
Tool Implementation
Use registerTool() method with descriptive names
Use registerTool() method with descriptive namesDefine schemas using zod for input and output validationProvide clear title and description fields - 04
Resource/Prompt Setup (Optional)
Add resources using registerResource() with ResourceTemplate for dynamic URIs
Add resources using registerResource() with ResourceTemplate for dynamic URIsAdd prompts using registerPrompt() with argument schemasConsider adding completion support for better UX
Permission review
Static risk signals and limitations
Writes files
The documentation asks the agent to create, modify, or delete local files.
Create proper .gitignore fileEvidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 80/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 37,126 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- github/awesome-copilot
- Skill path
- skills/typescript-mcp-server-generator/SKILL.md
- Commit
- 9933dcad5be5caeb288cebcd370eeeb2fc2f1685
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
Generate TypeScript MCP Server
Create a complete Model Context Protocol (MCP) server in TypeScript with the following specifications:
Requirements
- Project Structure: Create a new TypeScript/Node.js project with proper directory structure
- NPM Packages: Include @modelcontextprotocol/sdk, zod@3, and either express (for HTTP) or stdio support
- TypeScript Configuration: Proper tsconfig.json with ES modules support
- Server Type: Choose between HTTP (with Streamable HTTP transport) or stdio-based server
- Tools: Create at least one useful tool with proper schema validation
- Error Handling: Include comprehensive error handling and validation
Implementation Details
Project Setup
- Initialize with
npm initand create package.json - Install dependencies:
@modelcontextprotocol/sdk,zod@3, and transport-specific packages - Configure TypeScript with ES modules:
"type": "module"in package.json - Add dev dependencies:
tsxorts-nodefor development - Create proper .gitignore file
Server Configuration
- Use
McpServerclass for high-level implementation - Set server name and version
- Choose appropriate transport (StreamableHTTPServerTransport or StdioServerTransport)
- For HTTP: set up Express with proper middleware and error handling
- For stdio: use StdioServerTransport directly
Tool Implementation
- Use
registerTool()method with descriptive names - Define schemas using zod for input and output validation
- Provide clear
titleanddescriptionfields - Return both
contentandstructuredContentin results - Implement proper error handling with try-catch blocks
- Support async operations where appropriate
Resource/Prompt Setup (Optional)
- Add resources using
registerResource()with ResourceTemplate for dynamic URIs - Add prompts using
registerPrompt()with argument schemas - Consider adding completion support for better UX
Code Quality
- Use TypeScript for type safety
- Follow async/await patterns consistently
- Implement proper cleanup on transport close events
- Use environment variables for configuration
- Add inline comments for complex logic
- Structure code with clear separation of concerns
Example Tool Types to Consider
- Data processing and transformation
- External API integrations
- File system operations (read, search, analyze)
- Database queries
- Text analysis or summarization (with sampling)
- System information retrieval
Configuration Options
-
For HTTP Servers:
- Port configuration via environment variables
- CORS setup for browser clients
- Session management (stateless vs stateful)
- DNS rebinding protection for local servers
-
For stdio Servers:
- Proper stdin/stdout handling
- Environment-based configuration
- Process lifecycle management
Testing Guidance
- Explain how to run the server (
npm startornpx tsx server.ts) - Provide MCP Inspector command:
npx @modelcontextprotocol/inspector - For HTTP servers, include connection URL:
http://localhost:PORT/mcp - Include example tool invocations
- Add troubleshooting tips for common issues
Additional Features to Consider
- Sampling support for LLM-powered tools
- User input elicitation for interactive workflows
- Dynamic tool registration with enable/disable capabilities
- Notification debouncing for bulk updates
- Resource links for efficient data references
Generate a complete, production-ready MCP server with comprehensive documentation, type safety, and error handling.
Alternatives
Compare before choosing
coreyhaines31/marketingskills
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
event4u-app/agent-config
testing-anti-patterns
Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions
event4u-app/agent-config
design-review
Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.
event4u-app/agent-config
pest-testing
Use when writing, generating, or improving Pest tests for Laravel — clear intent, good coverage, maintainable structure, and alignment with project testing conventions.