Cortex RMCP MCP Server

What the code does

We read the source, 2 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.

postinstall: node scripts/install.js

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"); }

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

         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.

Connect this server

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 -- npx -y @dinglebear/cortex

{
  "mcpServers": {
    "cortex": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/cortex"
      ]
    }
  }
}

[mcp_servers.cortex]
command = "npx"
args = ["-y", "@dinglebear/cortex"]

{
  "mcpServers": {
    "cortex": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/cortex"
      ]
    }
  }
}

{
  "servers": {
    "cortex": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/cortex"
      ]
    }
  }
}

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).