harshal-mcp-proxy Now on npm: Single Daemon Replaces 12 MCP Server Configs

The MCP proxy that consolidates 12+ individual MCP server configurations into a single daemon is now available as an npm package. harshal-mcp-proxy ships as a 54 kB, 39-file compiled JavaScript package with TypeScript declarations and source maps. No more cloning, building, or manual systemd setup.

Installation

npm install -g harshal-mcp-proxy

This puts the binary in your PATH and includes a systemd service file that works with the npm binary path out of the box.

Quick Start

# Copy example config
cp $(npm root -g)/harshal-mcp-proxy/config.example.json ~/.config/harshal-mcp-proxy/config.json
# Edit with your MCP servers (API keys, endpoints, etc.)
vim ~/.config/harshal-mcp-proxy/config.json
# Quick test (stdio mode)
harshal-mcp-proxy
# Or daemon mode for multi-client shared use
harshal-mcp-proxy --daemon

Key Improvements Since Initial Release

• npm package: 54 kB, 39 files, compiled JS + TypeScript declarations + source maps
• systemd service file: now supports the npm binary path out of the box
• README: rewritten with npm install as the primary path
• Setup prompt: AI-pasteable setup script now uses npm install -g by default
• GitHub repo: homepage now points to the npm registry page

Compatibility

Existing users upgrading from source installation face no breaking changes. Config path is still ~/.config/harshal-mcp-proxy/config.json, the daemon continues to run on port 8765, and clients do not require any modifications. Just swap the old install for the npm version.

Benchmarks

The proxy replaces 12 separate MCP server configs with 6 tools, saving approximately 2.7 GB of RAM and 50K tokens per session. It uses MiniSearch (BM25) for local search and runs on TypeScript + MCP SDK + systemd.

Stack: TypeScript · MCP SDK · MiniSearch (BM25) · systemd