my-cool-proxy

My Cool Proxy is an MCP gateway that centralizes access to multiple MCP servers through a single proxy. It uses a Lua-based runtime to expose tools incrementally, reducing context window bloat and giving agents a progressive view of available servers and their tools. The gateway loads a default configuration on first run and allows clients to discover servers and tools in a structured, step-by-step manner. Agents can list servers, inspect server tools, view tool details, and then compose Lua scripts that invoke these tools in sequence or conditionally, all while keeping tool results contained and controllable by policy. This design enables more sophisticated, safe, and reusable MCP interactions across different backends (e.g., GitHub, databases, chat platforms) without exposing every tool upfront.

Key capabilities include:

• Progressive disclosure of servers and tools via list-servers, list-server-tools, and tool-details calls.
• Lua scripting to chain tool calls, perform conditional logic, and iterate results within a single execute() run.
• Gateway Skills that allow agents to discover, read, and execute reusable skill scripts through the MCP interface (disabled by default and configurable).
• A web dashboard and configuration options to tailor which tools and servers are exposed to agents, helping manage risk and context size.

Prerequisites:

• Node.js (LTS) and npm/yarn installed on your system
• Optional: access to a terminal with internet connectivity to install the package

Installation (global CLI usage):

• Install the package globally to use the CLI directly:

npm install -g @karashiiro/my-cool-proxy

• Run the proxy (default config auto-generates on first run):

my-cool-proxy

Alternative: run via npx without a global install:

npx @karashiiro/my-cool-proxy

Configuration:

• On first run, the gateway will auto-create a default config file and start with no servers configured. Find the config path by running:

my-cool-proxy --config-path

• Edit the generated config to add your MCP servers as described in the documentation (docs/configuration.md). You can start with a simple HTTP-configured server or expand with multiple MCP servers.

Tips and notes:

• By default, Gateway Skills are disabled to avoid conflicts with existing agent systems; enable them via the configuration docs if you plan to use Skill scripts.
• Use progressive discovery (list-servers, list-server-tools, tool-details) to minimize tool exposure and context size.
• If you plan to deploy in a multi-agent environment, consider configuring host and port accordingly and protecting the gateway with appropriate authentication/authorization measures.
• Review the configuration file for tool-filtering options to ensure agents only access permitted tools.
• Keep an eye on the MCP feature support table in the docs to track which protocol features are implemented by this server.