# Warmplane [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Warmplane/warmplane  
**GitHub Stars:** 5  
**npm Downloads (last month):** 2260492  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/warmplane

## Description
Local MCP control plane for persistent sessions and compact capability discovery.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "warmplane": {
    "command": "npx",
    "args": ["--arg","-y","--arg","@modelcontextprotocol/server-filesystem"]
  }
}
```

## Documentation

## What Warmplane MCP server does

Warmplane MCP server acts as a local control plane and reverse proxy for tool-calling agents. It maintains warm connections to multiple upstream MCP servers, then presents their capabilities through a single interface. This arrangement can reduce repeated schema transfer and gives operators one place to define aliases, access rules, profiles, approvals, and execution behavior.

Capability discovery is split into a compact catalog and on-demand detail retrieval. The catalog can be searched lexically or semantically, and SHA-256 ETags support cached capability responses. Tool aliases can replace upstream names or descriptions, while compact signatures describe required and optional parameters.

The execution layer includes retry classifications, crash-resilient idempotency keys, output context controls such as `_jsonpath` and `_limit_lines`, and chained batch calls with `$step.field` interpolation. Policy configuration supports allow and deny patterns, approval requirements, secret-key redaction, and per-profile server selections.

## How it works

Warmplane MCP server can run directly as a child process of an MCP client through `warmplane mcp-server`. It can also run as a persistent daemon, sharing state through a REST control plane, an embedded Web Control Deck, and an MCP endpoint configured for HTTP/SSE. Rust applications can use the `EmbeddedWarmplane` library without an HTTP child process or network hop.

The daemon exposes routes for capability listing and search, normalized tool calls, batch execution, asynchronous task updates, and the Web Control Deck. Health monitoring, circuit breakers, and process supervision are used to isolate slow or failed upstream processes, according to the project documentation.

## Setup and configuration

Install with Homebrew on macOS or Linux, Cargo, or a source build. The optional `semantic-search` Cargo feature enables local ONNX vector search through FastEmbed.

Add upstream servers interactively with `warmplane server add`, provide command- or URL-based server definitions, or import configuration from Claude Desktop, Cursor, OpenCode, or Zed. A JSON configuration file can define the listening port, tool timeout, aliases, policies, profiles, and `mcpServers` entries.

For direct client use, configure the client to launch `warmplane mcp-server` and pass the configuration path and optional profile. For shared operation, start `warmplane daemon --port 9090`. An HTTP/SSE MCP connection uses the configured `mcpHttpServer` endpoint.

## Tools and capabilities

Warmplane MCP server provides these documented interfaces and controls:

- Compact capability catalog retrieval and hybrid lexical/semantic search.
- Normalized tool execution with context distillation and idempotency keys.
- Batch tool calls with values passed between steps.
- Async task lifecycle handling and human approval review.
- Alias-based tool naming and description overrides.
- Profile-based server selection and policy enforcement.
- Secret redaction, audit-oriented telemetry, and health supervision.
- Embedded Rust execution through `EmbeddedWarmplane`.

The repository also includes an Agent Skill for supported coding-agent workflows and client configuration examples.

## Limitations and notes

Warmplane MCP server is a local control plane, so upstream MCP servers still need to be configured and available. Semantic search is optional rather than part of the basic Cargo installation. The provided examples use local stdio servers and local daemon addresses; they do not establish support for any particular upstream service.

_Full upstream README: https://allmcps.com/mcp/warmplane/readme_