mcp_server_exe

MCP Server.exe is a powerful executable that runs standard MCP services and provides advanced features such as tool chaining, multi-service orchestration (supporting SSE and stdio), a pluggable tool system, and auto-reload on config changes. You can launch it directly via the recommended CLI method or by using the packaged executable. This server is designed to connect multiple MCP services, manage complex automation workflows, and load custom tools through JavaScript configuration.

To use, start the server with a configuration file that describes your MCP services, tools, and deployment options. For example, you can run a standalone MCP service or combine multiple MCP services (some using SSE, others using stdio) in a single instance. The server also supports WebSocket mode for connecting to other MCP services, alignment with Cursor-based configurations, and tool chains that execute a sequence of tools with flexible data flow mappings.

Prerequisites:

• Node.js and npm or an environment capable of running Node-based npx commands (for the recommended npx method).
• Access to the MCP server executable assets (Windows/macOS builds) if you prefer using the packaged exe directly.

Installation steps:

1. Ensure your environment has Node.js installed. If not, install from https://nodejs.org/
2. Install or prepare the MCP Server executable assets (download the appropriate build for Windows/macOS).
3. Prepare an MCP configuration file (e.g., mcp.json) to describe your MCP servers, tools, and namespaces.
4. Start the server using the recommended npx approach shown in the README, or run the packaged executable directly. Example using npx:

npx mcp_exe --mcp-config ./examples/mcp.json

If you prefer running the packaged executable directly:

./executables/mcp_server-win-x64.exe --mcp-config ./examples/mcp.json

5. Verify the server is listening (default port 3000) and adjust via command line arguments as needed.

Notes and tips:

• The server auto-reloads when the --mcp-config or --mcp-js files change, so you can iterate configurations and plugin definitions without restarting manually.
• You can run multiple MCP services simultaneously, choosing SSE or stdio as the transport mode. Use --transport sse (default) or --transport stdio with each service definition.
• When using WebSocket mode, you can connect to external MCP services (e.g., via wss://) and aggregate them under a single MCP Server instance.
• If you encounter connectivity or hot-reload issues, ensure that the configuration file paths are correct and that the JSON syntax is valid.
• For embedding or automation, you can spawn the MCP server as a child process in your application and communicate via its stdout/stdin streams.