Action1

io.github.wyre-technology由 GitHub 帳號 wyre-technology 發布v1.1.5更新於 Oct 24, 2026

Action1 MCP server — endpoint inventory, patch visibility, and policy automation via REST API.

概覽

AI 產生的概覽

針對 Action1 的唯讀 MCP 伺服器,讓助理透過 Action1 REST API 檢視端點清單、缺少的修補程式與自動化原則。

可以做什麼
  • 依領域(組織、端點、原則、更新)探索可用工具
  • 列出可存取的 Action1 租用戶與受管裝置,並依 id 取得單一端點
  • 列出各端點缺少的作業系統與應用程式修補程式
  • 列出自動化、原則與修復規則
  • 在支援 MCP Apps 的宿主中呈現唯讀的互動式裝置摘要卡片
適用情境
適合管理 Action1、希望助理回答有哪些端點、缺少哪些修補程式、設定了哪些原則,同時不授予寫入權限的情境。
執行需求
以本機 stdio 程序執行(npx 或容器映像)。需要 Action1 API 憑證:用戶端 ID 與用戶端密鑰,以及基礎 URL 或租用戶識別碼;區域與預設組織為選用。HTTP 模式另需用於請求簽章的共用密鑰。
安裝前請注意
需要 Action1 API 用戶端密鑰,README 稱建立後無法再次取得。README 範例中的憑證變數名稱與清單所列不一致,安裝前請確認實際使用的名稱。未設定共用密鑰的 HTTP 模式僅供開發,且只綁定本機回環位址。v1 為唯讀,寫入類工具預計在後續版本提供。

安裝

在 SourceWeft 中

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

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

其他 MCP 客戶端

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

README

Action1 MCP Server

[MCP Compatible] [License]

MCP server for Action1 — endpoint inventory, patch visibility, and policy automation via the Model Context Protocol.

Read-only in v1. Deploy / automation surface is intentionally separated to a later release for blast-radius reasons (a bad policy push can brick endpoint fleets).

Tools

ToolDescription
action1_navigateDiscover available tools by domain (organizations / endpoints / policies / updates)
action1_list_organizationsList Action1 tenants accessible to the configured credentials
action1_list_endpointsList managed devices in an organization
action1_get_endpointGet a single endpoint by id
action1_list_missing_updatesList missing OS/application patches across endpoints — Action1's headline value-prop
action1_list_policiesList automation / policy / remediation rules

API surface maps to PSAction1 (Action1's MIT-licensed PowerShell module). When the v1 surface earns its keep, write tools (deploy, requery, package upload) come in v2 behind separate review.

Interactive Device Card (MCP Apps)

action1_get_endpoint renders as an interactive device-summary card in MCP Apps hosts (Claude Desktop/web) — status, OS, user, IP, agent version, reboot-required, and missing-update counts at a glance; plain-JSON behavior is unchanged in other hosts. The card is read-only (matching the v1 tool surface), neutral by default, and brandable via window.__BRAND__ injection or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL, MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG, MCP_BRAND_TEXT) — no rebuild needed.

Usage

Claude Desktop (MCPB)

Install via the MCPB bundle from the latest release.

Required credentials (created in Action1 → Settings → API Credentials, non-recoverable on creation — copy immediately):

  • API Key (Client ID)
  • Secret
  • Region (NorthAmerica default; also NorthAmerica-2, Europe, Australia)
  • Optional default organization id (for single-tenant use)

Stdio (direct)

bash
ACTION1_API_KEY=... \ACTION1_SECRET=... \ACTION1_REGION=NorthAmerica \ACTION1_DEFAULT_ORG_ID=org-... \npx -y github:WYRE-AI/action1-mcp

HTTP

CONDUIT_S2S_SECRET is required. If it is empty or a known placeholder (changeme, replace-with-a-real-secret, and similar), the HTTP server logs an error and exits non-zero. It never prints the secret. Generate one with openssl rand -hex 32.

MCP_HTTP_HOST defaults to 127.0.0.1 when unset. Set 0.0.0.0 only when CONDUIT_S2S_SECRET is set. The container image does that and sets AUTH_MODE=gateway. MCP_HTTP_PORT (or PORT) selects the port and defaults to 8080.

MCP_ALLOW_INSECURE_DEV=1 starts HTTP without CONDUIT_S2S_SECRET, logs a warning, skips X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) refuses to start. A placeholder secret is still rejected. Local development only.

/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.

X-Gateway-S2S

Every HTTP request except /health must include X-Gateway-S2S when a secret is configured. The value is t=<unix seconds>,v1=<hex>, where the hex is HMAC-SHA256 of the literal string t=<unix seconds> keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before vendor credentials are read.

bash
TS=$(date +%s)SIG=$(printf 't=%s' "$TS" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" -hex | awk '{print $NF}')curl -sS http://127.0.0.1:8080/ \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -H "X-Gateway-S2S: t=${TS},v1=${SIG}" \  -H "X-Action1-API-Key: $ACTION1_API_KEY" \  -H "X-Action1-Secret: $ACTION1_SECRET" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Gateway mode (AUTH_MODE=gateway)

The Docker image and Compose file default to gateway mode. Every request must include:

  • X-Action1-API-Key
  • X-Action1-Secret
  • X-Action1-Region (optional)
  • X-Action1-Default-Org-Id (optional)

A request missing the API key or secret gets 401 and does not fall back to ACTION1_API_KEY / ACTION1_SECRET in the process environment. Those headers are the only credential source for that request.

bash
docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -p 127.0.0.1:8080:8080 \  ghcr.io/wyre-ai/action1-mcp:latest

Compose refuses to start when CONDUIT_S2S_SECRET is unset, publishes 127.0.0.1:8080:8080, and does not pass static Action1 credentials into the container:

bash
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up
Single-tenant HTTP (AUTH_MODE=env)

Requests still require a valid X-Gateway-S2S header. Vendor credentials come from ACTION1_API_KEY and ACTION1_SECRET when the request does not carry those headers.

bash
docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -e AUTH_MODE=env \  -e ACTION1_API_KEY="$ACTION1_API_KEY" \  -e ACTION1_SECRET="$ACTION1_SECRET" \  -e ACTION1_REGION=NorthAmerica \  -p 127.0.0.1:8080:8080 \  ghcr.io/wyre-ai/action1-mcp:latest

Local HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning:

bash
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm start

Architecture

src/├── index.ts                  # stdio + HTTP transports, tool dispatch, S2S startup├── s2s-verify.ts             # X-Gateway-S2S HMAC-SHA256 check├── card.builder.ts           # MCP Apps device-card normalization + brand injection├── resources.ts              # resources/list + resources/read (ui:// device card)├── generated/│   └── device-card-html.ts   # committed vite single-file bundle (npm run build:ui)├── sdk/│   └── action1-client.ts     # embedded REST + OAuth client (factor-out candidate│                             # if surface crosses ~20 tools / 2+ domains)├── utils/│   ├── client.ts             # credential resolution (env vs gateway headers)│   └── types.ts              # DomainHandler interface├── domains/                  # one file per resource type│   ├── organizations.ts│   ├── endpoints.ts│   ├── policies.ts│   └── updates.ts└── __tests__/                # domain tests + MCP Apps contract testsui/                           # device-card source (index.html + device-card.ts)

Per-request credential isolation via AsyncLocalStorage — concurrent requests in HTTP mode never share credentials through process.env.

Development

bash
npm installnpm run buildnpm testnpm run dev      # tsc --watchnpm run lint     # eslintnpm run typecheck

License

Apache-2.0. See LICENSE.

來源:README.md,提交 8df2bcc

工具

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

版本歷史

1
  1. v1.1.5最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

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

  • 近 30 天內可連通25 分

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

  • 已宣告認證方式10 分

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

  • 已列出工具15 分

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

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