mcp -manage

This MCP server acts as a centralized management platform for multiple MCP (Model Context Protocol) servers. It provides a web-based UI to create, configure, start, stop, and monitor MCP servers, alongside tooling to deploy dynamic JavaScript tools, manage prompt templates, and issue access tokens for secure interactions. The backend persists data using SQLite and exposes RESTful APIs for server, tool, prompt, and token management, while enabling real-time status updates via Server-Sent Events (SSE).

To use the server, run the backend service (as configured in mcp_config) and connect the front-end client in your browser. Through the UI you can spin up MCP server instances, attach tools (JavaScript-based utilities that run within the MCP context), and define parameterized prompts. Tokens can be generated per server to control access, and you can copy MCP configurations for Claude Desktop or other MCP clients for seamless integration. The server also provides an endpoint to fetch the MCP configuration for each managed server, enabling automation and tooling integration.

Prerequisites:

• Node.js 14+ and npm/yarn installed
• Optional: PostgreSQL or SQLite support via the backend (SQLite is used by default in this repo)

Installation steps:

1. Clone the repository

git clone https://github.com/your-username/mcp-server-manage.git
cd mcp-server-manage

2. Install dependencies for both backend and frontend (if you plan to run the UI locally)

npm run install:all

3. Build the backend (TypeScript) if you plan to run in production mode

cd packages/backend
npm run build

4. Start the MCP Server Manager backend

# from the project root
npm run start:backend

5. Access the UI (if included in this setup) at the configured host and port (default http://localhost:3001)

Notes:

• Ensure the environment variables in mcp_config are properly set, especially PORT and DB_PATH.
• If you modify code, rebuild the backend before restarting.
• Refer to the API docs in the repo for programmatic access to servers, tools, prompts, and tokens.

Tips and common issues:

• SSE requires the server to be running and accessible at the configured port; verify with the health/status endpoints.
• If you enable token authentication, ensure the Authorization header is provided in client requests.
• The SQLite database file path should be writable by the backend process; check filesystem permissions if you encounter write errors.
• For local development, npm run install:all followed by npm run dev can streamline the workflow.
• When copying MCP configurations for Claude Desktop, verify that the target port and URL match the running backend instance.