Reticle MCP Server

What the code does

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

const CONTAINER_MARKERS = ['/.dockerenv', '/run/.containerenv'] as const;

    const child = spawn(cmd, args, { stdio: 'ignore', detached: true });

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.

  readdirSync,

# The Vite plugin bakes the bridge pairing token into the bundle at build time. A visitor's daemon
# only accepts a page carrying ITS token, so the demo bakes a known, PUBLIC one; the visitor starts
# their daemon with RETICLE_TOKEN set to the same value. Not a secret — never r…

  - '!{.env,.env.*,.npmrc,pnpm-lock.yaml}'

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 reticle -- npx -y @reticlehq/server

{
  "mcpServers": {
    "reticle": {
      "command": "npx",
      "args": [
        "-y",
        "@reticlehq/server"
      ]
    }
  }
}

[mcp_servers.reticle]
command = "npx"
args = ["-y", "@reticlehq/server"]

{
  "mcpServers": {
    "reticle": {
      "command": "npx",
      "args": [
        "-y",
        "@reticlehq/server"
      ]
    }
  }
}

{
  "servers": {
    "reticle": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reticlehq/server"
      ]
    }
  }
}