OpenClaw / ClawBot
OpenClaw (also called ClawBot) is a self-hosted AI agent with a built-in MCP client. Point it at Pingram’s hosted MCP server, sign in once, and the agent can use your Pingram account as tools.
General MCP setup for Claude, ChatGPT, and Cursor lives in the MCP guide.
Prerequisites
You already have OpenClaw installed and onboarding finished (chat works). For install itself, use openclaw.ai/install.
Prefer a model that handles tool calls reliably (Google Gemini Flash-class).
Small local models often drop required fields like type.
1. Add Pingram MCP (recommended)
In an OpenClaw chat, paste:
Add this MCP server. Transport is streamable-http and auth is oauth.
https://mcp.pingram.ioUse your account’s regional URL if needed:
| Region | URL |
|---|---|
| Default | https://mcp.pingram.io |
| Canada | https://mcp.ca.pingram.io |
| EU | https://mcp.eu.pingram.io |
OpenClaw should configure the server and open a browser for Pingram OAuth. Sign in with the same Pingram account you use in the dashboard, then return to chat when it finishes.
2. Install Pingram skills
In chat, paste:
List all pingram skills and let me choose which ones to install.3. Smoke test
Ask in natural language:
Send an email via Pingram to you@example.com with subject “OpenClaw test” and a short HTML body. Use notification type
openclaw_test.
Send an SMS via Pingram to +15551234567 saying “OpenClaw SMS test”. Use notification type
openclaw_test.
Email tools need type, to, subject, html. SMS tools need
type, to, message (prefer E.164). Check delivery in the
dashboard Logs.
Example payloads:
{ "type": "openclaw_test", "to": "you@example.com", "subject": "OpenClaw test", "html": "<p>OpenClaw MCP test</p>"}{ "type": "openclaw_test", "to": "+15551234567", "message": "OpenClaw SMS test"}Alternative: manual CLI / Settings
Use this if chat-driven setup fails, or you prefer the terminal.
PATH (once)
OpenClaw’s CLI lives in ~/.openclaw/bin. Add it permanently:
# macOS zsh — add to ~/.zshrc, then: source ~/.zshrcexport PATH="$HOME/.openclaw/bin:$PATH"Linux/bash: same line in ~/.bashrc. Windows: add
%USERPROFILE%\.openclaw\bin to your user PATH, then open a new terminal.
Add the server
CLI
openclaw mcp add pingram \ --url https://mcp.pingram.io \ --transport streamable-http \ --auth oauthSettings UI
- Open Settings → MCP → Add server.
- Name:
pingram - Transport: Streamable HTTP
- URL: your regional MCP URL
- Save
Sign in (OAuth)
openclaw mcp login pingramLeave that terminal open until the browser finishes. OpenClaw starts a local
callback (often http://127.0.0.1:8989/oauth/callback?...). If the CLI exits
early, the browser gets stuck on that URL — run openclaw mcp logout pingram,
then login again and keep the process running.
Optional code paste if login is still open:
openclaw mcp login pingram --code 'PASTE_CODE_ONLY'Switch accounts: logout, then login in a private browser window.
Confirm
openclaw mcp doctor pingram --probeYou should see tools such as pingram__email_send and pingram__sms_send.
Manual skill install examples:
openclaw skills install pingramopenclaw skills install pingram-emailopenclaw skills install pingram-smsOr search ClawHub / ask the agent to list Pingram skills.
Troubleshooting
| Symptom | What to try |
|---|---|
| Chat add / OAuth fails | Try the manual CLI / Settings path below |
command not found: openclaw |
Add export PATH="$HOME/.openclaw/bin:$PATH" to your shell profile, then reload |
Browser stuck on 127.0.0.1:8989/... |
CLI login was not running; logout then login again and leave the terminal open |
| Still the old Pingram account after login | openclaw mcp logout pingram, then login in a private browser window |
| Auth errors / tools die after ~1 hour | Re-auth: ask OpenClaw to reconnect Pingram MCP, or run openclaw mcp login pingram |
Sends fail with missing type |
Switch to a stronger model (Gemini Flash-class); always pass every required field |
| Tools missing after reconnect | Ask the agent to probe Pingram MCP, or run openclaw mcp doctor pingram --probe |
Security notes
- The agent acts as you, with access limited to your Pingram account.
- To disconnect, remove the
pingramMCP server in Settings or via the CLI, or revoke the MCP session from your Pingram account.