MCP Server
@kattatzu-resources
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.
Overview
What is MCP Server?
A robust, standard-compliant implementation of the Model Context Protocol (MCP) supporting SSE and STDIO transport for real-time communication with AI models. Built on Clean Architecture and SOLID principles, it enables extensible tools, resources, and prompts for developers.
How to use MCP Server?
Clone the repository, install dependencies with yarn, and build the project. Start the server with yarn start (or yarn rebuild for dev). Configure port via the PORT environment variable (default 3001). Use the MCP Inspector for testing: run npx @modelcontextprotocol/inspector node build/index.js and access http://127.0.0.1:6274.
Key features of MCP Server
- Full, standard-compliant Model Context Protocol implementation
- Dual transport support: SSE (HTTP) and STDIO (CLI)
- Clean Architecture with SOLID principles
- Extensible tools, resources, and prompts
- Comprehensive logging, error handling, and testing support
- Developer-friendly API with TypeScript and dependency injection
Use cases of MCP Server
- Building real-time communication channels between AI models and web applications via SSE
- Integrating MCP into CLI tools or local applications using STDIO transport
- Rapidly prototyping and testing MCP-based services with the MCP Inspector
- Extending AI model interactions with custom tools, resources, and prompts
- Creating maintainable, scalable server architectures for MCP-based systems
FAQ from MCP Server
What runtime does MCP Server require?
Node.js 18 or higher, with Yarn or npm as package manager.
How do I change the server port?
Set the PORT environment variable before starting; the default port is 3001.
How can I test my MCP Server implementation?
Use the official MCP Inspector tool: build and start the server, then run npx @modelcontextprotocol/inspector node build/index.js and access the Inspector UI at http://127.0.0.1:6274.
What transport methods are supported?
SSE (Server-Sent Events) for web applications/browser clients, and STDIO for CLI tools and local applications.
How do I extend the server with custom functionality?
Implement the ITool, IResource, or IPrompt interfaces and register them on the MCP server instance. Code examples are provided in the README for each extension type.
