內容簡介
Npcink AI Client Adapter 是一個專為 WordPress 設計的外掛，能夠將本地 AI 客戶端（如 OpenClaw 相容工具）透過專注的 REST 介面連接到 WordPress 網站，並提供穩定的操作環境以進行 AI 任務。
【主要功能】
• 連接 OpenClaw 相容的本地 AI 客戶端
• 檢查適配器的準備狀態與依賴性
• 提供機器可讀的 client_policy 以理解路由與數據邊界
• 通過 WordPress Abilities API 路由已批准的直接讀取請求
• 將寫入請求轉發至 Npcink Governance Core
• 支援經人類批准的最終執行
外掛標籤
開發者團隊
原文外掛簡介
Npcink AI Client Adapter connects local AI clients, such as OpenClaw-compatible tools, to a WordPress site through a focused REST adapter.
It is designed for sites that use Npcink Governance Core for reviewable AI operations and WordPress Abilities API providers, such as Npcink Abilities Toolkit, for concrete WordPress capabilities. The Adapter gives clients one stable WordPress REST surface for checking readiness, reading governance guidance, running approved read abilities, creating governed proposals, and executing supported writes only after Core approval and commit-preflight.
The default connection path uses signed key-pair pairing so the AI client does not need to receive a WordPress Application Password. A WordPress Application Password fallback is available for clients that already have a dedicated secret field or credential vault.
Adapter is intentionally thin. It does not define abilities, store approval truth, run workflow queues, act as an MCP server, manage model providers, store prompts, or execute arbitrary final write mutations. Governance remains in Npcink Governance Core. Ability definitions and callbacks remain in Npcink Abilities Toolkit or another WordPress Abilities API provider.
Adapter exposes a machine-readable client_policy on health, help, and the connection manifest so compatible clients can consume explicit route, output, sensitive-read, and write-flow boundaries. The local CLI also redacts profile paths, key ids, signing headers, tokens, passwords, and secrets from output, and its mcp subcommand runs a client-side stdio MCP server over the same signed profile with governed read, propose, preflight, and execute-after-human-approval tools only.
Current governed execution support covers explicit Adapter profiles after Core approval and commit-preflight: npcink-abilities-toolkit/trash-post, npcink-abilities-toolkit/create-draft, npcink-abilities-toolkit/update-post, npcink-abilities-toolkit/patch-post-content, npcink-abilities-toolkit/update-post-blocks, npcink-abilities-toolkit/update-template-blocks, npcink-abilities-toolkit/upsert-template-blocks, npcink-abilities-toolkit/update-template-part-blocks, npcink-abilities-toolkit/patch-setting-value, npcink-abilities-toolkit/set-post-seo-meta, npcink-abilities-toolkit/adopt-article-audio, npcink-abilities-toolkit/set-post-slug, npcink-abilities-toolkit/set-post-terms, npcink-abilities-toolkit/delete-term, npcink-abilities-toolkit/update-media-details, npcink-abilities-toolkit/upload-media-from-url, npcink-abilities-toolkit/set-post-featured-image, npcink-abilities-toolkit/optimize-media-asset, npcink-abilities-toolkit/replace-media-file, npcink-abilities-toolkit/restore-media-backup, npcink-abilities-toolkit/adopt-cloud-media-derivative, npcink-abilities-toolkit/rename-media-file, npcink-abilities-toolkit/delete-media-permanently, npcink-abilities-toolkit/delete-attachment, npcink-abilities-toolkit/reply-comment, npcink-abilities-toolkit/trash-comment, and npcink-abilities-toolkit/approve-comment.
Key features:
Connect OpenClaw-compatible and similar local AI clients to WordPress through one Adapter REST namespace.
Check Adapter readiness and dependency status before a client starts work.
Expose a machine-readable client_policy so clients can understand route, read, write, and sensitive-data boundaries.
Route approved direct-read requests through the WordPress Abilities API.
Forward governed write requests to Npcink Governance Core proposal and commit-preflight endpoints.
Support human-approved final execution for explicit, supported execution profiles after Core approval, plus a unified approve-and-execute action reserved for WordPress administrator sessions.
Prefer signed key-pair pairing for local clients, with an Application Password fallback when appropriate.
Keep channel, governance, ability, cloud, and model-provider responsibilities separate.
