內容簡介
VideoWhisper Site Manager 讓您透過 ChatGPT、Claude、Codex 和 Grok 等外部 SI/AI 代理管理 WordPress 文章和頁面，無需使用 API 金鑰，並保留自己的帳戶和訂閱。
【主要功能】
• 安全的 REST 層進行內容操作
• MCP 端點支援多種 AI 代理
• 提供 OpenAPI 架構 URL 進行 GPT Actions 匯入
• 指導性上手設置與官方連結
• 支援前端用戶連接短碼
• 安全控制與審計日誌功能
外掛標籤
開發者團隊
② 後台搜尋「VideoWhisper Site Manager for ChatGPT, Claude, Codex, Grok」→ 直接安裝（推薦）
原文外掛簡介
Requires WordPress 6.9 or later and PHP 8.2 or later. Optional native WordPress Abilities expose reviewed Site Manager reads and draft writes; the separate MCP Adapter remains optional. Use a currently supported PHP release; PHP 8.2 security support ends December 31, 2026.
VideoWhisper Site Manager lets you manage WordPress posts and pages through external AI/SI agents such as ChatGPT (Custom GPT + Actions), Claude (MCP), Codex (MCP), and Grok custom MCP connectors, using your own account, not API keys.
It exposes authenticated WordPress endpoints and setup guidance while you keep using your own AI account and subscription.
Included features:
Authenticated REST, MCP and generated OpenAPI interfaces for external agents.
Direct local OAuth with S256 PKCE, exact versioned per-tool consent, scopes, client management and revocation; no relay account required.
Optional native WordPress Abilities and separate MCP Adapter exposure, reviewed per user under Read Only or Safe Drafts.
Optional shared Turnkey relay, frontend connection help and native Application Password setup.
Free editorial tools for enabled content types, taxonomies, revisions, guarded recovery and signed-in draft previews.
Connection doctor, client configuration copy and credential-free diagnostics.
Opt-in image library/intake/metadata tools and effective standalone or Yoast SEO; details below.
Object permissions, HTTPS, publication controls, rate limits, audit logs and extension hooks.
The plugin does not call OpenAI, Anthropic, xAI, or any AI/SI provider directly. Your WordPress site exposes authenticated endpoints and setup guidance. You connect it to ChatGPT, Claude, Codex, or Grok yourself with your own account and subscription.
Supported Authentication
Local OAuth retains existing development/Pro setting keys and endpoint aliases for compatibility. Its canonical endpoints are under /wp-json/videowhisper-site-manager/v1/oauth/. Tokens authorize Site Manager APIs only, not the WordPress MCP Adapter or unrelated WordPress REST APIs. The local provider supports exact callback allowlisting and S256 PKCE with public/confidential registered clients; this is not a claim of universal client or complete current OAuth-spec support. Use HTTPS and the callback shown by your client. Native Application Passwords are a separate authentication path and are not per-tool OAuth grants.
The onboarding flow recommends using one authentication option for clarity, but development and migration setups can enable more than one.
Local OAuth – included in Free and selected on fresh installations with read-only site policy. Connect a compatible client directly to this site, add its exact callback URI to the allowlist, sign in and review requested scopes and individual tools. New or changed tools require renewed consent; refreshing a token never adds permissions. Writes and admin access are unchecked on the consent screen until selected.
Turnkey OAuth – optional for shared and multi-site workflows. Users connect through a compatible Relay & OAuth Server and can operate one or more connected sites from the same shared GPT or MCP connector.
Application Passwords – direct WordPress authentication over HTTPS using WordPress core Application Passwords. Best for admin-owned custom GPT/MCP setups where credentials are managed by the site operator.
Extension-provided authentication – developers can add custom OAuth, token validation, alternate connector metadata, or other authentication flows with the hooks listed below.
Permission modes and Free editorial workflow
Local OAuth offers quick selection buttons before approval:
Read Only selects available non-admin reads and the server denies write tools for this connection.
Safe Drafts can read permitted content and create/edit only draft or pending items. It cannot touch live/private items, publish, trash content, create taxonomy terms, or implicitly create tags. Assigning existing terms and restoring revision text still require object permissions and current versions. A draft default is enforced even if the site normally publishes new content.
Full Permissions selects every tool/scoped permission currently available in this request. It is not recommended outside a testing/development site. It cannot enable disabled site settings or bypass WordPress capabilities, and it never grants future tools automatically.
Custom starts from read access and lets you review tools individually. Narrowing a restricted preset retains its server-side restrictions; choose Custom for a different policy.
Safe Drafts limits the plugin’s supported core operations; installed third-party save hooks may have their own effects. Test with a dedicated least-privilege account and disposable content before production use. No mode is a human publishing approval system or a general sandbox for other plugins.
Enable public custom post types under Settings > Content (off by default), then reconnect to review the changed schemas. Use list_content_types and list_terms, create a draft, read its content_version, and supply expected_version on edits/term assignments/revision restoration. get_preview_link returns a WordPress preview that requires signing into WordPress as the connected editor; the URL is not anonymous access. Revisions restore title/content/excerpt only. Trash operations require WordPress Trash to be enabled, never permanently delete, and restore to draft. Older audit snapshots without the current taxonomy version may require manual review.
The new editorial module is available through this site’s direct Local OAuth or native WordPress authentication. Existing relay scope grants do not automatically gain it; relay per-tool consent is a separate future integration. Native Application Passwords still use WordPress/site permissions rather than the Local OAuth modes.
Optional native WordPress Abilities
Open Site Manager > Native Abilities. Access is off until an administrator enables it and saves a reviewed policy for a chosen site user. Start with Read Only. Safe Drafts adds permitted draft/pending operations; it cannot publish, modify live/private/scheduled content, trash items or create public terms. Site settings, WordPress capabilities, ownership, shared rate limits and audit still apply. Existing content is untrusted data, not permission to perform an operation.
Select individual tools and save the reviewed policy. New or changed contracts require review again; revocation takes effect on the next request. Policies bind the user, site, native resource, install epoch, profile version and selected canonical tool fingerprints. Uninstall revokes the epoch while retaining customer content and metadata; reinstall requires a new review.
The fixed owned namespace videowhisper-site-manager/ exports: get-site-context, list-content, get-content, list-content-types, list-terms, list-revisions, get-preview-link, create-content, update-content, assign-terms, restore-revision. There is no generic third-party ability executor or automatic exposure of other plugins. Native REST discovery: /wp-json/wp-abilities/v1/abilities. Read abilities use GET; draft writes use POST. Supply the ability’s input object. Reads return content_version; updates, assignments and restoration require the matching expected_version. Review the signed-in preview and publish manually in WordPress.
Core Abilities work without MCP Adapter. For MCP, optionally install and activate the official MCP Adapter from Plugins > Add New, and select Also expose these reviewed tools in this user’s policy. Connect a compatible native-authenticated client to /wp-json/mcp/mcp-adapter-default-server. Use that reviewed user’s WordPress Application Password over HTTPS; never paste credentials into a prompt or URL. Cookie REST clients also need a REST nonce. Adapter discovery and nested execution both honor the reviewed selection. Tested with official MCP Adapter 0.7.1; individual clients may require different authentication setup.
These policies constrain this plugin’s abilities; they do not narrow the Application Password itself. Other WordPress APIs still follow that user’s capabilities. Use a dedicated limited account. Site Manager Local OAuth remains the choice for a credential scoped to Site Manager tools; those tokens are not accepted by native Abilities or the separate Adapter endpoint. Native exposure neither changes existing OAuth grants nor requires a vendor account or an AI-provider API key.
Sample prompt (also available with a Copy button in Native Abilities): “Discover my permitted videowhisper-site-manager abilities and read the page I specify. Suggest an edit. Update only a draft/pending item using its fresh content_version as expected_version; otherwise create a new draft copy. Do not publish. Give me the WordPress preview link so I can review it while signed in.”
Current AI Actions and Tools
Available tools depend on site settings, authentication, exact consent and WordPress permissions. The registry feeds MCP, OpenAPI and the dynamic agent guide; grouped OpenAPI actions use an action subaction field.
Core: get_site_context, list_content, get_content, get_logs, create_content, update_content. Conditional recovery: revert_action, reset_action.
Direct native/Local OAuth editorial tools: list_content_types, list_terms, create_term, assign_terms, list_revisions, restore_revision, get_preview_link, trash_content, restore_content.
plugins_list lists compatible integrations, their agent instructions and visible tools. `get_site_context` includes a brief permission-aware integration summary. Other plugins attach through `vwsm_ai_plugin_integrations`.
Read /wp-json/videowhisper-site-manager/v1/agent-guide (Markdown), with ?format=json, ?surface=mcp or ?surface=actions for alternate formats. The generated guide describes the current site’s permitted tools.
Extension Hooks
Developers can extend this plugin without editing core files. Common hooks include:
Settings and admin UI: vwsm_settings_defaults, vwsm_settings_normalized, vwsm_admin_settings_save, vwsm_rest_settings_payload, vwsm_settings_tab_label, vwsm_settings_form_publishing_rows, vwsm_settings_form_security_rows, vwsm_settings_form_rate_limits_rows, vwsm_settings_form_logs_revisions_rows, vwsm_settings_form_turnkey_oauth_rows, vwsm_settings_form_authentication_rows, vwsm_settings_form_application_passwords_rows, vwsm_settings_form_content_rows, vwsm_settings_form_admin_rows, vwsm_settings_form_attachments_rows, vwsm_settings_form_fomantic_rows, vwsm_settings_form_after_core_rows, vwsm_auth_methods_section.
Authentication and OAuth metadata: vwsm_oauth_server_url, vwsm_authorization_server_url, vwsm_rest_401_headers, vwsm_external_oauth_onboarding_urls, vwsm_onboarding_oauth_tab_content, vwsm_handle_external_register_gpt.
OpenAPI, MCP, and tools: vwsm_ai_actions, vwsm_ai_plugin_integrations, vwsm_ai_plugin_option_integrations, vwsm_ai_plugin_action_dispatch, vwsm_ai_action_native_openapi_tools, vwsm_mcp_server_name, vwsm_mcp_extra_tools, vwsm_mcp_dispatch_tool, vwsm_mcp_site_context, vwsm_openapi_components, vwsm_openapi_document, vwsm_write_rate_limit_mcp_tools.
Content and sanitization: vwsm_allowed_content_types, vwsm_revision_limit, vwsm_revision_gradient, vwsm_supported_extra_allowed_html_tags, vwsm_allow_extra_allowed_html_tags.
User connection workflows: vwsm_user_connect_handle_post, vwsm_user_connect_after_sections, vwsm_user_connect_tools_data, vwsm_user_connect_gpt_url.
Operator and environment behavior: vwsm_default_operator_username, vwsm_use_current_user_mode.
Disclaimer
This plugin provides infrastructure for operating a WordPress site with external AI chatbots and agents. The site owner is solely responsible for the actions enabled through this functionality, including content created or changed by AI tools, credentials and access tokens, backups, privacy compliance, and any publishing or policy consequences.
AI-generated content can be inaccurate, defamatory, plagiarized, non-compliant, or otherwise unsuitable for publication. Review AI output and tool activity before publishing. Keep publishing disabled unless you fully understand and accept the risk.
Use HTTPS, protect Application Passwords and OAuth credentials, restrict access where possible, monitor logs, and maintain independent backups. Use at your own risk.
Frontend connection help
The [vwsm_user_connect] page provides section links, expandable app setup,
MCP URL copy buttons and a permission-aware tool list. Grok.com uses its custom
connector setup. Grok Bot has a separate Connect apps interface; custom MCP
availability depends on the product/account. Follow the linked provider guides.
Native WordPress abilities and optional MCP Adapter exposure have separate
administrator reviews. A connection can permit fewer tools than the account.
Personalized shortcode pages send no-cache headers; exclude them from any
reverse-proxy or full-page cache that ignores WordPress cache controls.
Privacy
Native Abilities availability is stored in site options. Reviewed policies are private user metadata scoped to the site; they contain selected tool fingerprints, mode, native version, audience, user and epoch, plus the optional Adapter exposure choice. No Application Password is copied into these policies.
Local OAuth stores client names, registered callbacks, registration IP addresses, user/client IDs, granted scopes, versioned tool selections and permission mode, token expiry and last-use timestamps in this site database. Access/refresh tokens use keyed hashes and confidential client secrets use password hashes. Credentials are returned only during issuance and are not included in tool/audit payloads. Administrators can revoke tokens and remove clients from Local OAuth. Deactivating Pro does not remove a Free-owned local connection.
This plugin stores the following data on your WordPress site:
Plugin settings in WordPress options (for example: publish, rate limit, HTTPS, IP allowlist, authentication, and provider URL settings)
Audit log entries in a custom database table (*_vwsm_audit_logs)
Optional dedicated operator user ID reference in WordPress options (when using onboarding helper)
Short-lived transient for one-time Application Password display after creation (plaintext is not stored long-term)
Short-lived transient cache for external bearer-token validation, when Turnkey OAuth is used
Optional connected service account tokens, site keys, server URLs, and provider policy links used for remote account and Turnkey OAuth workflows
A private vwsm_user_context user-meta value (up to 2,000 characters) when a user saves My Agent Context from [vwsm_user_connect]
Audit logs may include (depending on settings):
Authenticated WordPress user ID
Request route and method
Sanitized request/response summaries
Timestamp and IP address
This plugin does not send data to third-party AI services by itself.
This plugin does not include telemetry/analytics tracking by default.
Site owners are responsible for:
Securing the site with HTTPS
Managing WordPress users and Application Passwords
Configuring GPT sharing safely (recommended: Only Me)
Reviewing the privacy implications of any external AI service connected to the site’s API
External services
Optional user-selected image source
Only explicitly executed approved image intake sends a WordPress HTTP GET to the administrator-approved HTTPS source supplied by the agent/user. The source receives the URL (including any query), server network address and WordPress HTTP user-agent. Host validation may resolve DNS, including during a dry run. This feature supplies no WordPress login cookie, Application Password or OAuth token. The administrator chooses the destination and must review its terms/privacy policy. Manual editing, library reads, standalone SEO and disabled intake require no external image service. Source URLs and idempotency keys are redacted from audit summaries. The optional Connection doctor probe contacts only this site’s MCP endpoint without credentials.
This plugin can optionally connect to external services only when an administrator chooses a workflow that uses them, mainly as relay for multi site management. The default external services listed below are provided for free registration-based onboarding and multi site relay functionality. They do not require payment to use with the free plugin. Site administrators can also configure another compatible third-party Relay & OAuth Server URL or add custom services through the documented WordPress hooks.
Promptaur Relay & OAuth Server
Default service URL: https://server.promptaur.com
This service is used for optional multi-site relay routing (manage multiple sites from same session), shared Turnkey OAuth, shared GPT/shared MCP onboarding, and bearer-token validation on this type of setup. It makes setup simpler by allowing users to connect through one shared OAuth login and, when enabled by the service, use pre-existing shared GPT or MCP connector configuration instead of creating their own.
Data sent to this service:
When registering a site: the WordPress site URL, site name, and optional account or server registration token entered/configured by the administrator.
When registering a GPT/OAuth client: the site key, site secret, client name, and GPT callback URL supplied in onboarding.
When validating OAuth bearer tokens: the bearer access token plus the site’s registered site key and site secret. The plugin caches validation briefly according to the configured token cache TTL.
When loading Turnkey configuration, status, disconnect, or user connection data: the site key, site secret, and the specific account/site/user connection values needed for that request.
Terms of Use: https://server.promptaur.com/terms-of-use/
Privacy Policy: https://server.promptaur.com/privacy-policy/
VideoWhisper Remote Connect
Default service URL: https://consult.videowhisper.com
This optional onboarding service is used by the VideoWhisper Remote Connect wizard to register or log in a contact, import connection settings, and simplify account/site setup for multi-site relay server. It is a free registration-based service used to improve onboarding; it is not required for direct Application Password setup.
Data sent to this service from the onboarding page:
The client plugin identifier, WordPress site URL, and normalized site domain.
Registration/login details entered by the administrator, such as name, email address, PIN/confirmation code, website/domain, and form fields returned by the service configuration.
Remote account tokens returned by the service when the administrator chooses to import settings or push the current site URL/account state.
Terms of Use: https://consult.videowhisper.com/terms-of-use/
Privacy Policy: https://consult.videowhisper.com/privacy-policy/
