OpenClaw Setup

Prerequisites

pixcli installed and configured on the machine running OpenClaw
OpenClaw gateway running

Configuration

Add the pixcli MCP server to your OpenClaw configuration. Edit your openclaw.json:

{
  "mcp": {
    "servers": {
      "pixcli": {
        "command": "pix-mcp",
        "args": [],
        "env": {}
      }
    }
  }
}

With sandbox mode

{
  "mcp": {
    "servers": {
      "pixcli": {
        "command": "pix-mcp",
        "args": ["--sandbox"],
        "env": {}
      }
    }
  }
}

With custom config path

{
  "mcp": {
    "servers": {
      "pixcli": {
        "command": "pix-mcp",
        "args": [],
        "env": {
          "PIXCLI_CONFIG": "/home/user/.pixcli/config.toml"
        }
      }
    }
  }
}

Restart OpenClaw

After updating the configuration:

openclaw gateway restart

Usage

Once configured, you can use Pix operations from any connected channel (Telegram, Discord, etc.):

From Telegram

You: Check my Pix balance

OpenClaw: Your available balance is R$1,250.00.

You: Create a charge for R$75.00 with description "Freelance work"

OpenClaw: Charge created:
• TxID: abc123def456
• Amount: R$75.00
• Status: ATIVA
• Expires in 1 hour

You: Generate a QR code for my Pix key +5511999999999 for R$30

OpenClaw: Here's your Pix QR code for R$30.00.
[QR code image or BR Code payload]

From Discord

The same commands work from Discord channels where OpenClaw is active.

Troubleshooting

MCP server not starting

Verify pix-mcp is accessible from OpenClaw's environment
Check OpenClaw logs: openclaw gateway logs
Ensure the binary has execute permissions

Authentication issues

The MCP server runs as the same user as OpenClaw
Ensure ~/.pixcli/config.toml is readable by that user
Test independently: pix-mcp in a terminal to see startup errors

Slow responses

First call may be slow due to OAuth2 token acquisition
Subsequent calls reuse the cached token
Certificate loading happens once at startup

OpenClaw Setup

On this page