Install AgentPMT MCP Server for Openclaw

Prerequisites

You must have an active AgentPMT account. Prepare your credentials:

1. API Key: Generate from your Dashboard > Account > API Keys.
2. Budget Key: Generate from Dashboard > Budgets > [Select Budget] > Budget Keys.

Method 1: Automatic Setup via STDIO (Recommended for Desktop IDEs)

Run the interactive setup CLI tool to automatically configure your active IDEs (Claude Desktop, Cursor, Claude Code, etc.):

npm install -g @agentpmt/mcp-router
agentpmt-setup

Method 2: Manual Setup via STDIO

Step 1: Generate the Bearer Token

Combine your credentials into YOUR_API_KEY:YOUR_BUDGET_KEY and base64-encode them:

echo -n "YOUR_API_KEY:YOUR_BUDGET_KEY" | base64

Step 2: Configure Your Client

Claude Desktop Edit your configuration file (~/.config/Claude/claude_desktop_config.json on macOS or %APPDATA%\\Claude\\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "agentpmt": {
      "command": "npx",
      "args": ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"],
      "env": {
        "AGENTPMT_BEARER_TOKEN": "<your-base64-token>"
      }
    }
  }
}

Claude Code Add to your global or project .mcp.json / ~/.claude/mcp.json file:

{
  "mcpServers": {
    "agentpmt": {
      "command": "npx",
      "args": ["--package=@agentpmt/mcp-router@latest", "agentpmt-router"],
      "env": {
        "AGENTPMT_BEARER_TOKEN": "<your-base64-token>"
      }
    }
  }
}

Method 3: Direct HTTPS (For Programmatic Agents)

Connect directly using the endpoint https://api.agentpmt.com/mcp using standard JSON-RPC protocol over HTTP.

curl -X POST https://api.agentpmt.com/mcp \
  -H "Authorization: Bearer <your-base64-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-03-26",
      "clientInfo": { "name": "my-agent", "version": "1.0" },
      "capabilities": {}
    }
  }'

Configuration Schema

Regardless of your integration environment, the AgentPMT MCP connection uses a structured config schema. For desktop STDIO clients, write properties as environment variables:

Endpoint Schemas

When utilizing Openclaw Skills to manage programmatic integrations via Direct HTTPS, requests must implement the MCP 2.0 protocol over streamable HTTP: