Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • The install package comes from a different repo than this listing's
Own this project? Claim it
Warmplane logo

Warmplane

Local MCP control plane for persistent upstream sessions, compact capability discovery, governed tool calls, and multiple client interfaces.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Warmplane

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "warmplane": {
      "command": "npx",
      "args": [
        "--arg",
        "-y",
        "--arg",
        "@modelcontextprotocol/server-filesystem"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Warmplane MCP server keeps persistent connections to multiple upstream MCP servers and exposes them through one governed interface. It reduces capability-schema payloads with compact indexes, on-demand discovery, and ETag caching, while supporting aliases, policy checks, idempotency, approvals, and health supervision. Run it as a stdio MCP proxy, a daemon with REST and HTTP/SSE access, or an embedded Rust engine. Reach for it when agents need centralized control over several local or remote MCP servers.

Use cases

  • Aggregate several MCP servers behind one client connection
  • Reduce repeated tool-schema context in agent requests
  • Apply allow, deny, approval, and redaction policies
  • Run chained tool calls with idempotency protection
  • Expose MCP capabilities through REST or HTTP/SSE

Key features

  • Persistent upstream MCP connections
  • Compact capability catalogs with search
  • Tool aliases and parameter signatures
  • Idempotency, retries, and batch execution
  • Policy gates, profiles, and secret redaction
  • Stdio, REST, HTTP/SSE, and embedded Rust interfaces

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 42d

Supply-chain signal

2 high-severity advisories on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 0High 2Medium 0Low 0

Scanned 23h ago via OSV.dev · @modelcontextprotocol/server-filesystem (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads2.3MPackage downloads in the last 30 days.
Last commit20d agoMost recent push to the default branch.

How Warmplane works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Warmplane

Warmplane is an MCP server that connects AI clients to multiple upstream MCP servers through a local control plane. Its main tools and interfaces provide compact capability discovery, capability search, normalized tool calls, batch execution, policy enforcement, and optional task approval workflows over stdio, REST, or HTTP/SSE.

Install it with Homebrew, Cargo, or from source. Homebrew supports macOS and Linux; Cargo installs the published Rust package, while a source build uses the repository and can enable the optional `semantic-search` feature.

Configure the client to launch `warmplane mcp-server` as an MCP server. Pass the `--config` path and, when needed, a `--profile`; Warmplane also provides import support for existing Claude Desktop and Cursor configurations.

Yes. Run the daemon and configure `mcpHttpServer` to provide an HTTP/SSE MCP connection. The daemon also exposes REST routes for capability discovery, searches, tool calls, batch calls, and task updates.

Yes. Cursor is named as a supported MCP client and can launch Warmplane through the native stdio configuration. The repository also documents importing Cursor server configuration into Warmplane.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWarmplane AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/warmplane?style=directory)](https://allmcps.com/mcp/warmplane)
HTML Embed
<a href="https://allmcps.com/mcp/warmplane"><img src="https://allmcps.com/api/badge/warmplane?style=directory" alt="Warmplane on AllMCPs" /></a>