The mcp-server-demo is a basic MCP-compatible server designed to demonstrate the MCP server workflow in a minimal setup. It acts as a testbed for integrating MCP tooling, protocol negotiation, and simple command/handler capabilities typical of an MCP server. Use the server to verify basic connectivity, protocol handshake, and the ability to register and respond to simple MCP commands, tags, or events that you configure in your environment. Depending on your deployment, you can extend it with custom handlers, middleware, and example endpoints to illustrate how MCP commands are parsed and dispatched to user-defined logic.

Prerequisites:

• Node.js (v14+ recommended) and npm/yarn installed on your system
• A working internet connection to install dependencies

Installation steps:

1. Clone the repository (or download the demo package): git clone https://github.com/kaushik27-mcp/mcp-server-demo.git cd mcp-server-demo

2. Install dependencies: npm install

   or if you prefer yarn

   yarn install

3. Start the server:

   If a start script is defined in package.json

   npm run start

   If no start script exists, you can start directly with Node

   node server.js

4. Verify the server is running by connecting a client or checking the logs for a listening port (default 3000 or as configured).

Notes:

• Ensure any required environment variables (like PORT, HOST, or MCP-specific flags) are set before starting the server. See the environment section for details.
• If you encounter port conflicts, reconfigure the PORT in a .env file or through environment variables.

Common considerations:

• If your deployment environment uses Docker or a container orchestrator, ensure the container exposes the port configured by the server (default 3000 or as defined by your config).
• Check for MCP protocol compatibility in client code; this demo focuses on a minimal handshake and command dispatch pathway.
• Environment variables: PORT, HOST, and any MCP-specific flags should be documented in your deployment notes. If not present, the server may run on defaults.
• Logging: enable verbose logs during development to diagnose handshake or command routing issues.
• If you modify server.js or add new handlers, restart the server to apply changes.