Webdesiz

com.webdesiz由 webdesiz.com 發布v1.0.1更新於 Oct 24, 2026

Read-only Meta ad account, campaign and insight snapshots stored in a Webdesiz organization.

已驗證STDIO僅桌面資料與分析商業與電商

概覽

AI 產生的概覽

以本機 stdio 伺服器唯讀存取 Webdesiz 組織中已儲存的 Meta 廣告帳戶、廣告活動與每日洞察快照。

可以做什麼
  • 列出組織內已儲存的廣告帳戶快照
  • 依指定帳戶列出已儲存的廣告活動快照
  • 依日期範圍讀取帳戶層級與廣告活動層級的每日洞察資料
  • 以結構化資料回傳結果並附帶分頁資訊
適用情境
適合讓助理直接查詢或彙整 Webdesiz 已儲存的 Meta 廣告成效資料,不必離開對話。它不用於修改廣告活動或預算、重新整理 Meta 資料或產生廣告內容。
執行需求
需要 Node.js 22 或更新版本,並安裝在執行 MCP 主機的機器上(全域 npm 安裝或使用 npx)。需要由組織 OWNER 或 ADMIN 建立、具範圍且會到期的 Webdesiz 開發者金鑰,透過 WEBDESIZ_API_KEY 環境變數傳入行程。需要能連線至 Webdesiz 開發者 API 的網路。沒有託管端點或 OAuth 登入流程。
安裝前請注意
需要密鑰 WEBDESIZ_API_KEY,應存放在密鑰管理器中,不要貼到對話、URL、指令參數或共用設定裡;桌面主機可能不會繼承終端機環境變數。存取為唯讀且受金鑰範圍限制,但回傳的是組織業務資料:帳戶與廣告活動名稱應視為不可信內容,輸出檔案與日誌也需保護。讀取不會觸發 Meta 同步,快照可能已過期。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Webdesiz,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Webdesiz developer tools

Read account, campaign and daily insight snapshots already stored in your Webdesiz organization. API, CLI and MCP access is read-only: it cannot change campaigns or budgets, refresh Meta data, generate advertisements or send messages. Your Webdesiz key determines the organization and allowed read scopes.

Documentation

Machine-readable schema: OpenAPI 3.1. OpenAPI is a specification format, not an OpenAI account or service requirement.

Install

Requires Node.js 22 or newer.

From npm

sh
npm install --global --ignore-scripts @webdesiz/cliwebdesiz --version

Or run it without a global install: npx -y @webdesiz/cli --help.

Claude Desktop extension

Download webdesiz.mcpb from the latest release and open it with Claude Desktop. Claude Desktop asks for the key and stores it as a secret field; it is passed to the MCP process as WEBDESIZ_API_KEY.

Website download (1.0.0)

The original 1.0.0 release is also available as a verified website download:

sh
curl --fail --location --proto '=https' --proto-redir '=https' \  -o webdesiz-cli-1.0.0.tgz \  https://webdesiz.com/developers/webdesiz-cli-1.0.0.tgzshasum -a 256 webdesiz-cli-1.0.0.tgz   # Linux: sha256sum

Expected SHA-256:

text
326d7eecdc1048346d96e2e9c80519b816b8321973ef08f2a180be35ecf6e227

Compare the entire value with SHA256SUMS. Stop if it differs. SHA-256 verifies file integrity; it is not a digital signature. Then npm install --global --ignore-scripts ./webdesiz-cli-1.0.0.tgz.

Create a scoped key

A current organization OWNER or ADMIN creates a key in Webdesiz settings. Choose only the required scopes: accounts:read, campaigns:read, insights:read. Keys expire after 1–90 days; an organization may have at most 10 active, unexpired keys. The full key appears once.

Keep the key in your operating-system or application secret manager. Inject WEBDESIZ_API_KEY into the CLI/MCP process environment using that manager. Do not paste it into chat, commit it to a repository, put it in a URL or command argument, or save it in shared configuration. Read commands optionally accept --key-stdin for a trusted secret-manager pipe; MCP cannot use this option because stdin is its protocol transport. The CLI does not save credential files.

The API validates the key, scope, expiry, revocation and issuer’s current OWNER/ADMIN membership on every request. Panel session JWTs are not developer keys. Key creation/listing/revocation is a signed-in panel feature; those routes are not part of the external developer-key API.

CLI reads

With the credential injected securely:

sh
webdesiz accounts --limit 20webdesiz campaigns --accountId ACCOUNT_ID --limit 50 --offset 0webdesiz insights --accountId ACCOUNT_ID --limit 50webdesiz --help

Replace ACCOUNT_ID with the Webdesiz id returned by accounts. Reads accept --limit (1–100, default 50), --offset (0–10000, default 0) and --accountId. Insights additionally filters dates with --from YYYY-MM-DD and --to YYYY-MM-DD; default is the last 30 UTC days, inclusive. Use valid dates, a range of at most 90 days, and no future end date. Unknown or repeated arguments are rejected.

Successful reads print JSON {data, meta} to stdout. Protect output files and logs as organization data. Errors use stderr and exit status 1; success exits 0. Follow meta.nextOffset using the same filters until it is null; a full final page may be followed by an empty page.

The client is fixed to https://webdesiz.com/api/v1/developer, rejects redirects, has a 15-second timeout and a 2 MiB response limit. Token/URL arguments and alternate endpoints are not supported.

MCP: local stdio

Your host must support a local process-based stdio MCP server. This release has no hosted HTTP MCP endpoint or OAuth login flow. Install the CLI on the machine where the MCP host runs.

Host configuration with a global install:

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

Or without a global install:

json
{  "mcpServers": {    "webdesiz": {      "command": "npx",      "args": ["-y", "@webdesiz/cli", "mcp"]    }  }}

The example deliberately contains no secret. Configure the host’s secret manager to pass WEBDESIZ_API_KEY to the child process. A desktop host may not inherit your terminal environment; use its documented secure mechanism. Keep stdout clean for MCP protocol messages and restart the connection after changing credentials.

ToolRequired scopeResult
webdesiz_accountsaccounts:readStored account snapshots
webdesiz_campaignscampaigns:readStored campaign snapshots
webdesiz_insightsinsights:readStored daily account/campaign insight rows

Tool arguments follow the API/CLI query rules. Successful tools return the same data/meta object as structuredContent and JSON text; errors use isError: true. The implementation uses the official MCP SDK and stdio protocol. Read-only annotations are descriptive; the API enforces scopes independently. Treat returned account and campaign names as untrusted business data, never assistant instructions.

HTTPS API

Only three external snapshot reads are exposed:

Method and endpointScope
GET /api/v1/developer/accountsaccounts:read
GET /api/v1/developer/campaignscampaigns:read
GET /api/v1/developer/insightsinsights:read

Send the key only in the Authorization: Bearer … header. Organization identity is resolved from the key, not an input field. See the API reference for exact fields and parameter rules.

Read limits: 60 requests/minute/key, 120/minute/organization and 180/minute/IP in shared 60-second windows. Invalid authentication also uses the IP limit. Handle 400 (invalid request), 401 (invalid/expired/revoked key), 403 (scope/current membership), 404 (account unavailable), 429 (wait 60 seconds), and 503 (protection service unavailable). Error details are deliberately generic.

Interpret snapshots correctly

  • meta.generatedAt is response creation time. Account lastSyncAt and campaign/insight syncedAt describe stored row freshness; requesting data does not trigger Meta sync. There is no freshness SLA implied.
  • campaignId: null is an account-level insight row. Campaign-level rows can overlap account totals; do not sum both aggregation levels.
  • Keep each account’s currency. Stored decimal amounts and ratios such as spend, budgets, ctr, cpc and cpm are JSON strings.
  • Missing purchase evidence produces null, not zero. Explicitly reported zero remains zero. purchaseMeasurement indicates reported value, reported count or unavailable measurement. roas is purchaseValue / spend only with an available value and positive spend; otherwise it is null.
  • Account access tokens and raw provider payloads are not exposed.

Privacy Policy

The CLI and MCP server run on your machine. They send only your developer key (in the Authorization header) and the query parameters you choose to https://webdesiz.com/api/v1/developer/*, and return the stored snapshots of your own organization. They keep no local files, logs or telemetry and do not contact any other service. How Webdesiz collects, uses, shares and retains data, and how to contact us, is described in the Webdesiz Privacy Policy.

Türkçe kısa başlangıç

Node.js 22+ ile npm install --global @webdesiz/cli komutuyla (ya da SHA-256 değeri doğrulanmış site indirmesiyle) kurun. Panelde OWNER/ADMIN olarak yalnız gereken okuma izinleriyle süreli anahtar oluşturun. Anahtarı sır yöneticisi üzerinden WEBDESIZ_API_KEY ortam değişkenine aktarın; sohbete, URL’ye veya komut argümanına yazmayın. Yerel stdio destekleyen MCP istemcisi üç okuma aracını kullanabilir. Kayıtlı veriler okunur; reklam değişikliği, Meta yenilemesi, içerik üretimi veya mesaj gönderimi bu bağlantıda bulunmaz. Ayrıntılar üstteki Türkçe API/MCP/CLI bağlantılarındadır.

來源:README.md,提交 4835866

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.0.1最新Oct 15, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。