mcpServers

mcpServers is a lightweight MCP (Model Context Protocol) server runner designed to host multiple MCP server instances under a single process. The configuration object allows you to define one or more named MCP servers, each with its own runtime command and arguments. This setup makes it easy to scale and manage several MCP-related services from one place. Once started, clients can interact with each configured server via the MCP protocol, using the defined ports and endpoints as determined by the runtime configuration. Typical usage involves starting the process and then addressing each sub-server by its configured name or port as documented in the server’s runtime output.

Prerequisites:

• Node.js (LTS version) installed on your system
• npm or yarn for package management

Installation steps:

1. Clone the repository or install via npm if published: git clone https://github.com/trezero-mcpservers/mcpServers.git cd mcpServers

2. Install dependencies: npm install

3. Configure your mcpServers in the mcp_config.json (or as part of environment if supported). The provided example uses a single server named 'trezero-mcpservers'.

4. Start the server: node server.js

5. Verify the server is running by checking logs or connecting with an MCP client to the configured port (default 3000 from the example).

Notes:

• If you publish the package, you can install via npm and run a single command to start with a config file.
• Adjust the environment variables as needed for your deployment (PORT, MCP_ENV, etc.).

Tips and common issues:

• Ensure the port you configure is open in your firewall and not used by another process.
• If you deploy multiple MCP servers under the same instance, ensure each has a unique name and, if applicable, distinct ports.
• Check logs for startup errors related to missing dependencies or misconfigured environment variables.
• Validating your MCP configuration before starting can save debugging time; use JSON validation tools on your mcpServers object.
• If you upgrade Node.js, re-run npm install to refresh dependencies.
• Consider adding a process manager (like PM2) for auto-restart and monitoring in production.

Environment variables of interest:

• PORT: The listening port for the main MCP server (default 3000)
• MCP_ENV: Runtime environment indicator (e.g., development, production)
• Any per-server overrides can be added under each server's env block in the mcp_config.