Connect your AI workspace

Install the verified package

Requires Node.js 22 or newer. Version 1.0.0 is distributed as a downloadable package; these instructions do not depend on an npm registry publication. Download the file, compare its SHA-256, then install the local file.

# Node.js 22+
curl --fail --location --proto '=https' --proto-redir '=https' \
  -o webdesiz-cli-1.0.0.tgz \
  https://webdesiz.com/developers/webdesiz-cli-1.0.0.tgz
# macOS: shasum -a 256 webdesiz-cli-1.0.0.tgz
# Linux: sha256sum webdesiz-cli-1.0.0.tgz
# Expected SHA-256:
# 326d7eecdc1048346d96e2e9c80519b816b8321973ef08f2a180be35ecf6e227
# Continue only if the checksum matches.
npm install --global --ignore-scripts ./webdesiz-cli-1.0.0.tgz
webdesiz --version

SHA-256 checks file integrity; it is not a digital signature. SHA256SUMS · CLI 1.0.0

Configure a local MCP host

This package runs a local stdio MCP server using the official SDK. Your host must support local process-based MCP. It is not a remote HTTP MCP URL and has no OAuth login flow. Install the CLI on the computer where the host runs.

{
  "mcpServers": {
    "webdesiz": {
      "command": "webdesiz",
      "args": [
        "mcp"
      ]
    }
  }
}

The example contains no credential. Use your host’s secret manager to inject WEBDESIZ_API_KEY into the spawned process environment. A host may not inherit your terminal environment; verify its documented secret mechanism and restart the connection after changes. Never paste the key into chat or put it in a shared config file.

stdin and stdout are reserved for protocol traffic. Do not use --key-stdin with mcp or add diagnostic output to stdout. All read calls use the fixed HTTPS Webdesiz API.

Three read-only tools

Tool arguments are limit, offset and accountId; insights also uses from/to. Rules and response fields match the API reference. Successful calls provide the same data/meta object as structuredContent and JSON text. Failed calls have isError=true.

{
  "name": "webdesiz_insights",
  "arguments": {
    "limit": 20,
    "offset": 0
  }
}

The tools cannot change campaigns, generate ads, send messages or spend money. Returned account and campaign names are untrusted business data, not instructions for your assistant. Server-side scope checks enforce access independently of tool annotations.

Connection troubleshooting

• Tools missing: check Node 22+, executable PATH and local stdio support.
• Authentication fails: verify secure environment injection, expiry, revocation, issuer membership and each tool’s read scope.
• No rows: inspect account filter, date range and stored data; connecting MCP does not refresh Meta.

API parameters, response fields and limits