Arcane RMCP MCP Server

What the code does

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

  const install = spawnSync(process.execPath, [installer], { stdio: "inherit" });

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.

    if std::path::Path::new("/.dockerenv").exists()

        credentials_file="$HOME/.aws/credentials"

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 rarcane -e 'RARCANE_API_URL=<RARCANE_API_URL>' -e 'RARCANE_API_KEY=<RARCANE_API_KEY>' -- npx -y @dinglebear/rarcane

{
  "mcpServers": {
    "rarcane": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/rarcane"
      ],
      "env": {
        "RARCANE_API_KEY": "<RARCANE_API_KEY>",
        "RARCANE_API_URL": "<RARCANE_API_URL>"
      }
    }
  }
}

[mcp_servers.rarcane]
command = "npx"
args = ["-y", "@dinglebear/rarcane"]
env = { RARCANE_API_URL = "<RARCANE_API_URL>", RARCANE_API_KEY = "<RARCANE_API_KEY>" }

{
  "mcpServers": {
    "rarcane": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/rarcane"
      ],
      "env": {
        "RARCANE_API_KEY": "<RARCANE_API_KEY>",
        "RARCANE_API_URL": "<RARCANE_API_URL>"
      }
    }
  }
}

{
  "servers": {
    "rarcane": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/rarcane"
      ],
      "env": {
        "RARCANE_API_KEY": "<RARCANE_API_KEY>",
        "RARCANE_API_URL": "<RARCANE_API_URL>"
      }
    }
  }
}

Put your own values in place of <RARCANE_API_URL> (Arcane API base URL), <RARCANE_API_KEY> (Arcane API key or bearer token). The author’s registry entry marks them as required.

Optional settings from the registry entry, left out of the block above: ARCANE_RMCP_VERSION (Optional GitHub release tag override for the downloaded Arcane RMCP binary), ARCANE_RMCP_REPO (Optional GitHub owner/repo override for release asset downloads), ARCANE_RMCP_RELEASE_BASE_URL (Optional release download base URL override), RUST_LOG (Tracing filter for Arcane RMCP logs).