box by Simular 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.

      const candidate = path.join(dir, bin + ext)

    spawn(command[0], command[1], { stdio: 'ignore', detached: true, shell: false, windowsVerbatimArguments: false }).on('error', () => {}).unref()

      if (entry === 'aws') return [read(path.join(home, '.aws/credentials'), 'secrets/aws')]

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

claude mcp add box --transport http https://relay.simular.cloud/mcp

https://relay.simular.cloud/mcp

[mcp_servers.box]
url = "https://relay.simular.cloud/mcp"

{
  "mcpServers": {
    "box": {
      "url": "https://relay.simular.cloud/mcp"
    }
  }
}

{
  "servers": {
    "box": {
      "type": "http",
      "url": "https://relay.simular.cloud/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Endpoints