Install
Give your agent Wabi
The Wabi MCP server gives an agent every op: the sandbox, the onboarding checklist, members, keys, billing and every product area as it ships. Pick your tool; most sign in through your browser, so there is no key to copy.
Claude Code
claude mcp add --transport http wabi https://getwabi.dev/api/mcpRun this in a terminal, then type /mcp in Claude Code, pick wabi and sign in with your browser. To use an API key instead, add --header "Authorization: Bearer wabi_…".
Codex
# ~/.codex/config.toml
[mcp_servers.wabi]
url = "https://getwabi.dev/api/mcp"
bearer_token_env_var = "WABI_API_KEY"Add this to ~/.codex/config.toml and export WABI_API_KEY (an API key from Integrations in the dashboard, or from npx @meterapp/wabi login).
Cursor
{ "mcpServers": { "wabi": { "url": "https://getwabi.dev/api/mcp", "headers": { "Authorization": "Bearer wabi_…" } } }}Add this to .cursor/mcp.json (or ~/.cursor/mcp.json for every project). Leave out headers to sign in with OAuth from Cursor's MCP settings.
ChatGPT or any MCP client
https://getwabi.dev/api/mcpAdd a custom connector with this URL (ChatGPT: Settings → Connectors). The client signs you in through the browser; no key needed.
CLI
npx @meterapp/wabi loginnpx @meterapp/wabi opsNode 20 or later, nothing to install. Every op is a command; stdio-only MCP hosts can run the CLI's MCP bridge.
Then ask for something real
“Show me what is left to set up in Wabi, then send a test message from our sandbox number and make the customer reply.” Every client's config, API keys and the stdio bridge are in the MCP docs.