Install
openclaw skills install @millerm30/pingramSend email and SMS and manage a Pingram account via hosted MCP in OpenClaw. Use when the user wants Pingram notifications, delivery logs, phone numbers, or sender domains.
openclaw skills install @millerm30/pingramPingram is a notifications platform (email, SMS, and more). In OpenClaw, use the hosted MCP server — do not invent REST calls or ask for an API key when MCP is available.
Docs: https://www.pingram.io/docs/integrations/openclaw
MCP: https://mcp.pingram.io (Canada: https://mcp.ca.pingram.io · EU: https://mcp.eu.pingram.io)
Tell the user to run:
export PATH="$HOME/.openclaw/bin:$PATH"
openclaw mcp add pingram \
--url https://mcp.pingram.io \
--transport streamable-http \
--auth oauth
openclaw mcp login pingram
openclaw mcp doctor pingram --probe
Use the regional URL that matches their Pingram account. After login, tools are
prefixed (for example pingram__email_send, pingram__sms_send).
Always include every required field. type is a free-form label for Logs /
Insights (for example openclaw_test) — never omit it.
pingram__email_sendRequired: type, to, subject, html.
{
"type": "openclaw_test",
"to": "user@example.com",
"subject": "Hello from OpenClaw",
"html": "<p>Sent via Pingram MCP</p>"
}
pingram__sms_sendRequired: type, to. Include message with the body text.
{
"type": "openclaw_test",
"to": "+15551234567",
"message": "Hello from OpenClaw"
}
Prefer E.164 for phone numbers (+ and country code).
After connect, the agent can also look up delivery logs and manage phone numbers, inboxes, sender domains, accounts, and A2P-related tools exposed by the MCP catalog. Prefer listing tools / probe output over guessing names.
If tool calls fail validation because fields like type are missing, ask the
user to switch to a stronger model. Small local models often drop required
arguments; Gemini Flash-class models handle Pingram tools reliably.
If tools return auth errors or stop working after roughly an hour, have the
user re-run openclaw mcp login pingram.