Get the FREE Ultimate OpenClaw Setup Guide →

MCP

🚀 Enterprise MCP Server with Admin Panel & Role-Based Security Production-ready Model Context Protocol server with FastAPI backend, React frontend, and advanced security features. ✨ Features: Admin Panel • RBAC • AI Analytics • File Management • Real-time Streaming Built with FastAPI, React, and modern web technologies.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio jatin23k-mcp-server node path/to/server.js \
  --env PORT_BACKEND="8000" \
  --env PORT_INTERFACE="3001"

How to use

This MCP server provides a backend service and a lightweight interface for managing the MCP. The backend runs on port 8000 and exposes health checks at http://localhost:8000/health, while the interface (UI) is served on port 3001 at http://localhost:3001/mcp-interface.html. You can start the server using the included Windows one-click startup script START-MCP.bat, which launches both components automatically and opens your browser to the interface. Once running, you can edit the code and refresh the browser to see changes instantly. If you need to stop the server, close the windows started by the batch file or press Ctrl+C in the terminal.

Typical workflow:

  • Start the MCP with the provided batch script or run the server.js entry directly if you are operating outside Windows.
  • Open the interface URL to interact with the MCP dashboard.
  • Use the backend health endpoint to verify the server is alive.

How to install

Prerequisites:

  • Node.js (and npm) installed on your system
  • Access to the repository containing this MCP server

Installation steps:

  1. Clone or download the repository: git clone https://github.com/jatin23k-mcp-server/repo-name.git cd repo-name
  2. Install dependencies: npm install
  3. Start the MCP server:
    • On Windows: run START-MCP.bat (one-click start)
    • Or manually start the server with Node (if you know the entry point): node path/to/server.js
  4. Verify that the backend and interface are running:

Notes:

  • The batch script automatically opens the interface in your browser and enables file uploads.
  • Ensure ports 8000 and 3001 are not in use by other processes.

Additional notes

Tips and common issues:

  • If the interface does not load, ensure the backend server started correctly on port 8000 and that there are no firewall restrictions blocking ports 8000 and 3001.
  • If you change code and don’t see updates, reload the interface page (F5) or restart the batch script.
  • The default verification endpoints are:
  • If you deploy to a different environment, update the PORT_BACKEND and PORT_INTERFACE environment variables as needed.
  • Ensure persistence and file upload paths are correctly configured in your environment to avoid runtime errors.

Related MCP Servers

Sponsor this space

Reach thousands of developers