Cortex RMCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 1 Oct 2026.
Rust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
if (!fs.existsSync(binary)) { const installer = path.resolve(__dirname, "..", "scripts", "install.js"); const install = spawnSync(process.execPath, [installer], { stdio: "inherit" }); if (install.status !== 0) fail("binary is not installed; postinstall may have failed"); }
DO UPDATE SET count_in_window = count_in_window + excluded.count_in_window",
source: Some("/var/run/docker.sock".to_string()),
.map(|h| h.join(".ssh/config"))
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add cortex-rmcp -- npx -y cortex-rmcp
{
"mcpServers": {
"cortex-rmcp": {
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
]
}
}
}
[mcp_servers.cortex-rmcp]
command = "npx"
args = ["-y", "cortex-rmcp"]
{
"mcpServers": {
"cortex-rmcp": {
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
]
}
}
}
{
"servers": {
"cortex-rmcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
CORTEX_HOME (Optional Cortex home directory containing configuration and local SQLite data), CORTEX_TOKEN (Optional bearer token for Cortex MCP HTTP mode; also used by some shared configs), CORTEX_API_TOKEN (Bearer token for Cortex REST API routes when running daemon/API mode), CORTEX_RMCP_VERSION (Optional GitHub release tag override for the downloaded Cortex binary), CORTEX_RMCP_REPO (Optional GitHub owner/repo override for release asset downloads), CORTEX_RMCP_RELEASE_BASE_URL (Optional release download base URL override), RUST_LOG (Tracing filter for Cortex logs).
Rust MCP and CLI server for Docker, host inspection, SSH, logs, ZFS, and safe file operations.
Rust MCP server and CLI for Arcane Docker and container management.
Host, Docker, Compose, SSH, logs, ZFS, and file operations over MCP and CLI.
TypeScript MCP server for AI-powered containerization workflows with Docker and Kubernetes support
Docker for AI agents — containers, compose stacks, logs and databases, locally or over SSH.
MCP server for managing Fly.io machines, apps, logs, and Docker images.
MCP server for Docker — containers, health checks, Compose, logs, monitoring for AI agents
Rust MCP server and CLI for Unraid GraphQL, NAS, Docker, VM, and storage workflows.
Answers built from our own checks of this server.