mcp
A clean architecture MCP server implementation with support for multiple transports (SSE and STDIO). Provides extensible tools, resources, and prompts following SOLID principles for real-time AI model communication.
claude mcp add --transport stdio kattatzu-resources-mcp-server node build/index.js \ --env PORT="Server port (default 3001)"
How to use
This MCP server implements the Model Context Protocol with support for multiple transports, including SSE (Server-Sent Events) and STDIO, enabling real-time communication with AI models. It exposes an API surface built on a clean architecture, with modular tools, resources, and prompts that can be extended as needed. The server is designed to run on Node.js 18 or higher and can be operated via standard Node tooling or the included build/start workflow. Typical usage involves starting the server, then connecting clients through either the SSE endpoint for web-based apps or the STDIO channel for CLI and local tooling. The inspector tool can be used to validate the MCP implementation against the protocol and interact with the server through the CLI.
How to install
Prerequisites:
- Node.js 18 or higher
- Yarn or npm (your preferred package manager)
Step-by-step installation:
-
Clone the repository git clone https://github.com/your-username/mcp-server.git cd mcp-server
-
Install dependencies yarn install
or npm install
-
Build the project (if applicable) yarn build
or npm run build
-
Run the server yarn start
or npm run start
-
Optional: Run a development build and watch yarn rebuild
or npm run rebuild
Notes:
- By default, the server listens on port 3001 unless PORT is overridden in the environment.
Additional notes
Tips and common considerations:
- Transport choices: SSE is suitable for web browser clients; STDIO is convenient for CLI tools and local applications.
- Environment Variables: PORT configures the listening port (default 3001). Other runtime options may be available depending on deployment (check the codebase for additional env vars).
- If you modify or extend the server with new tools/resources/prompts, follow the existing patterns to ensure compatibility with the MCP protocol.
- When testing, use the MCP Inspector tool to validate messages and end-to-end flow against your server at http://127.0.0.1:6274 UI.
- Ensure Node.js version is ≥ 18 and that you have a suitable TS build output (e.g., build/index.js) when running the server directly with node.
Related MCP Servers
iterm
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
editor
MCP Server for Phaser Editor
DoorDash
MCP server from JordanDalton/DoorDash-MCP-Server
mcp
MCP сервер для автоматического создания и развертывания приложений в Timeweb Cloud