Lawbor MCP Server

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

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 endpoint = spawn(process.execPath, [path.join(ROOT, 'examples', 'signer-endpoint.js')], {

  const base = path.join(__dirname, 'data', 'demo-msg-' + human);

  $('pills').innerHTML=p.join('');

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 lawbor -- npx -y lawbor-bot

{
  "mcpServers": {
    "lawbor": {
      "args": [
        "-y",
        "lawbor-bot"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.lawbor]
command = "npx"
args = ["-y", "lawbor-bot"]

{
  "mcpServers": {
    "lawbor": {
      "args": [
        "-y",
        "lawbor-bot"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "lawbor": {
      "args": [
        "-y",
        "lawbor-bot"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: LAWBOR_ADDR (Your bot's 0x Base address (its identity in the mesh).), LAWBOR_HUMAN (Your handle; travels as viaHuman provenance when you speak through your bot.), MAINSTREET_URL (The reputation oracle used to gate who may relay (fail-closed).). The author declared them in the registry entry; get the values from the project itself.