mcp -kit

MCP Server Kit is a TypeScript-based starter template for building MCP servers. It provides a structure for three MCP primitives—Tools, Resources, and Prompts—along with code generation tooling to scaffold new components. The server is designed to be run as a standard Node.js application and serves the MCP endpoints defined by your prompts, resources, and tools. The compiled server is expected at dist/server.js, which is what the MCP runtime will execute.

To use the kit, install dependencies, build, and run the server. The template includes working examples for prompts, resources, and tools to illustrate patterns you can extend. You can scaffold new components using the provided generators and then rebuild. When the server is running, clients that support MCP can interact with the Tools (actions the LLM can perform), Resources (read-only data exposed to the LLM), and Prompts (reusable templates with arguments).

Prerequisites:

• Node.js (recommended via NVM: nvm use <your-version> as specified by the project)
• npm (or pnpm/yarn if preferred by your workflow)

1. Clone the repository: git clone <repository-url> jamielivingstone-mcp-server-kit cd jamielivingstone-mcp-server-kit

2. Install dependencies: npm install

3. Build the project (transpile TypeScript to dist/): npm run build

4. Run the server (production or development): node dist/server.js

5. Optional: Run linting and formatting during development: npm run lint npm run format npm run lint:fix

6. If you add new components (prompts/resources/tools), regenerate and rebuild: npm run generate npm run generate:prompt npm run generate:resource npm run generate:tool npm run build

Notes:

• The server entry point is dist/server.js after a successful TypeScript build.
• You can extend the MCP surface by adding new prompts, resources, and tools under src/, and then regenerating and rebuilding.
• The project uses Biome for linting/formatting and Zod for schema validation, so ensure your new definitions conform to those patterns.
• If you plan to deploy, consider exposing relevant environment variables (e.g., database connection strings, API keys) via the env section in the mcp_config for secure runtime configuration.
• Check MCP client compatibility for features like elicitation or sampling; many clients may not yet support these advanced capabilities as of early 2026.