| 开发者 | videowhisper |
|---|---|
| 更新时间 | 2026年11月19日 21:35 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
videowhisper-site-manager plugin folder to /wp-content/plugins/, or install it via the WordPress Plugins screen./mcp.[vwsm_user_connect]; Activate offers to create that page. Both screens show the current account’s connection instructions, first workflow, personal tools and context. No permission is granted merely by opening a screen. Long setup and safety guidance is under Site Manager > Help.
Client setup
Use Site Manager > Onboarding for the current provider-specific links, exact callbacks, copy buttons and client commands. For a direct connection, choose included Local OAuth, add the exact callback shown by your client to its allowlist, then sign in and review the displayed scopes/tools. Turnkey relay and native Application Passwords are alternatives with separate authentication boundaries.
ChatGPT Custom GPT Actions can import the generated OpenAPI schema. Claude, Codex and compatible Grok custom connectors can use the MCP endpoint. Provider/client availability and subscriptions vary; instructions link their official documentation. Never paste passwords/tokens into prompts or URLs. Start with Read Only and verify a legitimate read before enabling draft writes.
Supported Authentication
Local OAuth retains existing 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.
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, plus enabled list-media, get-media, set-featured-image, get-seo, update-seo and propose-seo-changes. Owned exports remain fixed. Eligible public third-party abilities can be imported individually under Reviewed abilities, with separate source/schema review and exact connection consent; no automatic exposure occurs. 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."Tool titles, feature groups and Read/Write labels help you review available actions. Callable tool IDs and saved approvals stay unchanged. A reader can still require administrator access. Saving a private proposal is a write; a preview that saves nothing is a read. Optional display metadata never grants a tool or overrides personal limits.
Activate WooCommerce 11.3 or newer with its native product abilities (WooCommerce 11.3 requires WordPress 7.0). In Tool access, review list_product_drafts, get_product_text and propose_product_text_changes for the intended roles and any restricted connection. Read permits discovery; Draft permits private proposals. New tools are never added to existing grants automatically; personal exclusions remain in force. Native WordPress Abilities need their own reviewed user policy. The separate MCP Adapter is optional.
Ask: "Find the draft product named Example, read its current text, and propose a clearer description. Keep it a draft and send me the WordPress review link." A person compares the exact before/after fields in Review changes and applies them within ten minutes. Only existing simple draft products and name, description and short description are supported. The plugin uses WooCommerce's fixed native update operation, not arbitrary post meta or a generic ability executor.
Names are limited to 1,000 UTF-8 bytes, descriptions to 32 KiB, short descriptions to 8 KiB and encoded proposals to 256 KiB. Safe post HTML is accepted without silent rewriting. Shortcodes, blocks, builders, variable/other product types and larger snapshots require the native WooCommerce editor. Read the fresh product version after a conflict; an interrupted application stays blocked from replay. Prices, stock, files, images, customers, orders and publication are not managed by these tools. The plugin does not call an external service for this local workflow.
Resource safeguards are easy to review in Settings, Resources, beside Rate Limits. Request frequency and request size/time/concurrency are independent: changing a resource allowance never grants a tool or clears a user's personal restrictions. Existing resource bookmarks continue to work. Independent extensions may add settings panels through vwsm_resource_settings_tabs_v1 without a private dependency.
Use a shared relay for a small administrator/editor team managing several sites in one agent session. Use the included local OAuth server when many or all site users need agents for their own content. Neither connection path changes WordPress roles, ownership, reviewed tool scopes or personal restrictions. Start in Onboarding, review Quick setup, connect on AI/SI Agents, then use the read-first workflow. Connection doctor diagnoses one exact missing tool before you change permissions or refresh a client catalog. Help keeps longer setup and workflow explanations out of the main forms. Compatible authenticated integrations can negotiate small verified extension flags bound to the current user, connection and issuer. Missing or malformed optional flags grant no new access; existing authentication, personal tool restrictions and native approvals remain authoritative. Configurable local Resources safeguards bound ordinary content JSON input, parsed complexity, complete read results and active operations. The content service applies read budgets across REST, MCP and native WordPress Abilities. Media and integration upload contracts keep their existing limits. Operator ceilings and trusted extension allowances can only reduce the effective local ceiling; tool permissions and personal restrictions remain independent.
With a compatible current Agentic Multilingual Translator, translation_review_queue lists your own editable public page/post work. Included text tools list permitted registered sources, read bounded context, save private plain-text drafts, update private notes and separately publish when configured permissions permit. Supported comments, bios, reviews and labels require an enabled adapter that re-reads the public source and verifies ownership and operation permissions. Arbitrary options/usermeta and private content are not exposed. Native corrections remain protected, source changes conflict, and notes do not refresh stale translation text. Site-wide configured messages and other users are outside these own-content tools; integrations may add separately authorized administration through extension hooks. New tool approvals never clear existing restrictions. Native setup/review links are under Multilingual Translator > Plugin texts / Review queue.
With compatible current Translator releases, translation_plan_refresh reuses verified unchanged units and retains protected manual corrections. SEO fields travel with the complete private draft; publication remains separate. Refresh discovery and review changed field/protection tool contracts when required. Safe Drafts supports own-content refresh but cannot publish, unlock fields or select administrative scope.
Shared private editorial progress notes accompany editable content and can be read/updated with get_content_notes/update_content_notes. Agents can record review/completion work for editing, optimization and translation without changing public content. Updates require the latest notes version; notes are bounded plain text, retained on uninstall and excluded from public page output. Notes never grant tool or publication permission.
For the optional Translator integration, start with translation_status to check setup and find native settings/review links. A site administrator opts into integration access, configures languages and reviews the allowed role/client tools. Own-content draft tools and separately enabled publication keep their existing ownership and permission checks. Additional integrations may extend administration through separately approved tools and documented hooks.
With the compatible Translator, inspect private source differences and propose local language URLs for your own content. Publication separately applies a proposal and retains earlier paths. New URL publication semantics require the applicable connection review; native section protection remains under human control.
Use Settings → Turnkey OAuth → Refresh plan and status. This uses the stored site key and secret; it does not register the same URL again, rotate credentials or approve tools. Current servers can refresh CRM metadata immediately, with a one-minute repeat-request cooldown. Normal requests may show cached information while a stale plan is queued for refresh. Older servers use their normal cache interval. Do not remove registration to synchronize a plan.
When this plugin is installed on a CRM site, it also supplies an optional notification provider through vws_crm_service_notification_providers_v1. A compatible CRM integration can opt in through its native server-sync controls and reuse the existing registered HTTPS relay connection. Enable change notices on both ends. The CRM sends an event ID and the changed account/plan ID using the stored site registration credentials; customer account tokens, contact details and plan values are not sent. The receiving server reads authoritative CRM metadata. No tool permissions are granted by a notice.
Open AI Site Manager > Relay permissions and choose the WordPress account. The account screen shows current site approval mode, Admin/Other Roles presets, the account override, verified clients and recommended permission-contract updates. Eligible clients and changed previously selected tools are checked. Review selected approvals or Approve all recommended tools for all clients, inspect the exact review, then Approve. Tools excluded by a client mode remain excluded; revoked or invalid clients require individual review. Use Preset from Now selects Read Only, Draft, Write or an eligible administrator mode for current/future verified relay clients. It follows current site-approved tools inside that ceiling; it does not approve disabled site features, personal exclusions, new packages or unrelated integrations. Exact restricted clients remain restrictive unless the administrator explicitly reviews replacement for the checked active clients. Review each client is available for high-stakes accounts. The site-wide default can follow configured role presets while retaining account overrides. The configuration link opens the extra-review section in Tool access. Every change is a native administrator POST with CSRF protection, an operator/session-bound short-lived exact review, current configuration/catalog checks and one-use apply. Bulk approval needs transactional WordPress metadata tables. Existing individual reviews also reject stale account snapshots. Upgrading does not change live approval policy.
Optional Agentic Multilingual Translator integration adds six typed tools: translation_languages, translation_sources, translation_context, translation_save_draft, translation_review and translation_publish. Users can translate only their own editable public Posts/Pages in enabled site languages. Contexts bind user, site, source hash, target version, current Translator settings and expiry. Enable access in Multilingual Translator > Settings and review the exact tools in Site Manager > Tool access and the connection. Safe Drafts permits private translation drafts; publication additionally needs both plugins' publication controls and WordPress publishing capability. Existing restricted grants and personal exclusions remain in force. Start with one clean Activate screen: select allowed roles, choose Admin/Other Roles presets and review exact changes before continuing directly to your first workflow. Advanced connection reviews stay separate. Extra per-relay-client administrator review is optional and off on a fresh installation; upgrades retain the existing mode until a native administrator explicitly changes it. Custom/restricted/revoked grants and personal tool exclusions remain authoritative. Choose an SEO improvement from real search evidence. The optional read-only Search Console adapter uses your existing permitted Site Kit connection, returns bounded page/query metrics and clearly labeled review candidates, then guides your assistant to a private single-item SEO proposal. You review exact changes in WordPress before publishing them. No extra Google credentials or automatic SEO edits. Manage multiple linked WordPress sites from one AI app connection and the same agent session with the optional hosted Turnkey relay. Install Site Manager on each site, link the intended users to the same relay account, and name the target site in each request. Separate WordPress installations are supported; a WordPress Multisite network is not required. Each site keeps its own roles, reviewed tools and connection permissions. Hosted account limits and explicit connection consent apply; direct Local OAuth remains available without the hosted service. Let each WordPress user narrow agent access from the connection page: Read Only, Draft, Safe Write, Power Write, eligible administrator modes or Custom. Group tools by feature, keep Draft protection when customizing, and restore the site ceiling without altering connection grants. Administrators can select feature groups in Tool access. Personal limits cover Site Manager APIs and its owned native Abilities; they do not restrict unrelated WordPress APIs or manual editing. Set separate Admin and Other Roles limits with Disabled, Read, Draft, Write, Admin, Develop or Custom presets. Review the exact tools before saving, filter the Tool access matrix and customize individual selections. Admin and Develop are administrator-only. Presets retain WordPress capabilities and separate integration approvals; upgrading does not change existing access. For the optional relay, choose whether a second administrator review is required for each account/client. Existing installations retain their review mode until explicitly changed. API feature switches follow the reviewed tools; duplicated switches are replaced by Tool access links. Site Read Only and publication controls remain authoritative; a preset does not unlock writing or establish authentication. Prepare one content or image change for a clear native human review: compare exact before/after fields, preserve native blocks and keep the original unchanged until an authorized person applies it. Optional private proposals work under Safe Drafts, expire after ten minutes and recheck the source permission, object version and publication policy. Shared image metadata requires separate permission; no file upload or publication status is changed by a proposal. The optional SEOPress 10.4+ adapter uses four native WordPress Abilities to read/update title, description, canonical and noindex with vendor role restrictions. SEOPress remains the rendering owner, inherited noindex stays protected, and compatible page caches are purged after an SEO write. It does not enable the vendor external REST switch or add duplicate tags. Prepare a concrete SEO change for one item, compare before/after values in WordPress, then apply with a human review. Optional Agentic Optimization integration uses its own editor and renderer, including per-item noindex, while preserving manual editing and avoiding duplicate SEO output. Relay tools require the reviewed site role policy or an exact per-client review when that extra mode is enabled. Existing restricted or revoked policies remain authoritative. Review eligible installed WordPress abilities individually; source or schema changes withhold them until reviewed again. 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:
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.
After Activate, open AI/SI Agents, connect your app, then open Try your first workflow after connecting. The same guide is included below the app instructions on [vwsm_user_connect]. Copy one prompt at a time to verify a read, prepare a disposable draft, and request a private content proposal. The guide reflects the current WordPress account’s site and personal tool limits; the connected agent may have fewer grants. Nothing runs automatically, no permissions are changed, and no usage analytics are collected. Review the exact before/after in WordPress before applying, then trash the test draft.
Select Rank Math native ability (read only) in Settings > Images and SEO when Rank Math v1.0.272+ is active. get_seo executes only the owner’s native post SEO read, honoring its capabilities and item access. It returns resolved title, description, canonical and robots/noindex data. It does not expose all Rank Math abilities, write private vendor metadata, change indexing, or emit additional tags. Use the Rank Math editor to apply recommendations. Yoast, SEOPress, Agentic Optimization and standalone providers retain their existing supported workflows. Changing providers requires current SEO tool consent. Rank Math’s own optional services and tracking retain their separately configured consent.
Enable private item proposals under AI Site Manager → Images and SEO, then review the new tools for your connection. Ask the assistant to read get_content or get_media, prepare propose_content_changes or propose_media_changes using the returned version, and open the native review URL. Compare the exact fields and apply while signed in as a permitted user. Proposals expire after ten minutes and do not change the target until applied. Public/shared changes require current publication permission.
Yes. Select AIOSEO title and description (single-item review) in Settings > Images and SEO with AIOSEO 4.9.8+ and its native post SEO abilities available. Current AIOSEO is recommended. Enable SEO tools and review the changed get_seo / propose_seo_changes permissions in Tool access and any restricted connection. Existing approvals do not automatically acquire a new provider contract. Ask your assistant to read get_seo, propose only title/description with that seo_version, and return the WordPress review URL. An authorized human reviews the exact before/after and applies it there. No direct AIOSEO update tool is exposed. Safe Drafts can save a private proposal without changing public output; application still requires current source, reviewer, publication and vendor permissions. Values are stored overrides, not resolved frontend previews. Blank values restore AIOSEO defaults and smart tags resolve through AIOSEO. Older AIOSEO may require saving an item in its native editor before its abilities can read it; update AIOSEO or follow that editor step. The adapter never falls back to private-table writes. It leaves canonical, indexing, social, schema, keyphrases and publication state unchanged, adds no rendering tags, and requires neither the MCP Adapter nor a new external account. Other configured AIOSEO services keep their separate consent. Compatible local page caches are purged after application; external CDNs may need a separate purge.
Yes. Select SEOPress under Images and SEO with SEOPress 10.4+ and Titles and Metas enabled. Site Manager calls its four fixed owner abilities; vendor SEO role restrictions still apply. Inherited noindex cannot be removed here. Selecting this adapter does not enable SEOPress external REST exposure. It adds no rendering tags or second metadata store. Remote hosting/CDN caches may need their own purge.
A relay must advertise permission contract v1. Open AI Site Manager > Onboarding > Activate > Quick setup to review Admin and Other Roles presets. Extra client admin review is optional on that same screen: when off, verified eligible connections use the reviewed role preset. Custom, Read Only, Safe Drafts and revoked client policies remain restrictive; existing Full selections follow the role policy only after this native mode-change review. Existing installations retain their previous requirement until changed. Extra review mode binds an exact allowlist to the connected WordPress account and verified issuer/client under Relay permissions. Revocation never falls back. Native WordPress Abilities retain separate per-user grants and optional MCP Adapter exposure. Context writes remain excluded from Safe Drafts. Under Reviewed abilities, select up to 20 eligible public abilities from installed plugins. Private abilities, this suite's exports and MCP Adapter bridge helpers are excluded. Source or schema changes require another review. Imported tools use stable identifiers and the owner's native schema/permission checks. They require administrator access; writes also require publication enabled and are excluded from Safe Drafts. Review these new identifiers in the intended connection separately. Imported abilities do not become owned native exports. Installed plugin code remains trusted; this is not a general sandbox.
Enable SEO tools under Images and SEO and choose a ready provider. Agentic Optimization must have its standalone editor enabled and own SEO output. Ask the assistant to read get_seo, then create propose_seo_changes using the returned seo_version. The proposal can refer to an editable live item without changing public metadata. Open its WordPress review URL, compare the exact fields and apply there. The proposal expires after ten minutes; changed content/provider/permissions require a new review. No agent approval boolean can apply it. Other SEO providers keep ownership of their own rendering.
Open Site Manager > Connection doctor, choose the site account, affected verified relay connection and missing tool, then run the read-only check. It distinguishes unavailable modules, role reviews, personal restrictions, connection selections and changed definitions. Existing permissions are never saved or expanded. Optional client observations and tool fingerprints help identify stale metadata without asking for a token. Exact review links and a redacted copy/export support handoff. Endpoint/configuration and recovery help stay available in a closed section. The optional reachability check sends one anonymous request to this site's endpoint only; it does not verify client credentials. WordPress cannot observe a client chat's loaded catalog. Refresh tools in the client and start a new conversation when necessary; refreshing a site connection does not add tools or permissions. Under Site Manager > Settings > Images and SEO, enable only the required modules. Existing settings and grants retain the prior storage-only SEO behavior. New tool names require exact local OAuth, native Abilities or relay permission review. New workflows are not exposed to unversioned relay grants.
list_media, get_media and set_featured_image use the enabled image module and object capabilities. Featured-image selection requires fresh content_version. Safe Drafts can select an existing image on draft/pending content without editing shared image metadata.upload_media_from_url requires a separate reviewed Local OAuth tool selection or native WordPress authentication, upload capability, an editable target/current version and a 16–80 character idempotency key. Intake creates a public Media Library URL even for drafts. It is excluded from Safe Drafts. Administrators approve at most 20 exact HTTPS source hostnames. No redirects, credentials, private/reserved addresses, SVG, GIF or animated intake. JPEG/PNG/static WebP must fit 8 MiB or the lower host upload limit and the 16 MP/memory budget. Dry runs resolve/validate the hostname but perform no HTTP image download or attachment save. Identical retries reuse the attachment; conflicting reuse is rejected. Failed temporary files are cleaned.update_media requires explicit shared-metadata and publication settings, WordPress publication/edit capabilities and current media_version. Shared alt/caption/title/description edits can affect live pages. Read Only/Safe Drafts exclude this tool.get_seo reports the provider, stored title/description/canonical and seo_version. update_seo requires the current version and changes only supplied fields; empty strings clear them. Preview with dry_run before applying. Draft policies remain enforced; live/private/scheduled edits require publication permission._vwsm_* metadata behavior and makes no effective-output claim. Standalone opts into public singular title/description/canonical rendering and yields to recognized Yoast, Rank Math, AIOSEO, SEOPress or The SEO Framework ownership. It is not a full sitemap/schema/redirection suite. Yoast uses only its fixed native get/update post SEO abilities and vendor permissions; tested with Yoast 28.7. Yoast must have indexables enabled/built; local/staging environments may intentionally disable those abilities. No vendor table writes, provider credential storage or unrestricted execute-any-ability wrapper is included. Other vendor write adapters remain future work.list_media, get_media, set_featured_image, get_seo, update_seo) when their modules are enabled. Review them per user; public intake and shared image edits remain outside that draft-only bridge. Private SEO proposals may reference an editable published item without changing it; apply them in the native Review changes screen. Optional MCP Adapter exposure keeps the same consent checks.
Prompt: "Find my draft about [topic]. Read its version, list accessible images and preview a featured-image selection. Save only the reviewed draft. Do not upload or change shared images. Read get_seo, suggest a title/description, preview with dry_run, then apply only the approved fields with its fresh seo_version. Leave canonical and publication status unchanged."
Image/SEO responses report supported previous values; no universal undo or transaction across third-party editors/save hooks is promised. Mutation locks serialize this workflow's writers only. After publication, verify the actual page source and purge any independent hosting/CDN cache as needed.
No. This plugin does not store or use any AI/SI provider API keys. Your agents or AI/SI apps connect to this plugin. Plugin does NOT connect directly to AI/SI services.
Yes, you can connect agents or applications (i.e. ChatGPT, Claude, Grok Bot) that use your free account or paid subscription from their providers (i.e. OpenAI, Anthropic, xAI).
Use a compatible Streamable HTTP MCP client. Client availability depends on the provider, product version and account. Release 1.3.1 was verified with the official TypeScript MCP SDK 2.3.1, including TLS, discovery, authorization, refresh and revocation. The setup tabs provide guidance for popular clients; this does not guarantee every app version or account tier.
The plugin includes site-owned Local OAuth with explicit scopes and versioned individual tool selection, plus optional Turnkey OAuth and WordPress Application Passwords. Turnkey OAuth uses a compatible Relay & OAuth Server for shared GPT/MCP workflows. Application Passwords use WordPress core HTTP Basic Authentication over HTTPS. Developers can add more authentication flows with the documented hooks.
Version 1.3.1 requires an explicit, versioned selection of individual tools. Existing settings, client registrations and audit data remain, but tokens issued without these permissions require a one-time reconnection. Only selected unchanged tools remain usable; newly added tools, contract changes and expanded publication permission require another review. Token refresh cannot expand access. These per-tool grants apply to included Local OAuth, not native WordPress Application Passwords or the optional relay service.
Read the item with get_content, review its content_version, preview the intended change with dry_run, and pass that version as expected_version when saving through Local OAuth. A stale version returns a conflict instead of overwriting a later edit. Creating content defaults to draft. Responses include a request ID and, where available, an audit log ID. Supported update snapshots can be reverted/reset only if the current owned fields match the expected snapshot and permissions still allow the operation. This is not an undo guarantee for third-party effects or unsupported fields.
Site content, users, settings, client registrations and audit data are retained. Local access/refresh tokens are revoked and a reinstall requires a new permission review. Plugin cleanup jobs are removed. Deactivating the plugin alone does not delete customer data.
Not by default. Creating published content or changing an already live item is blocked unless an administrator enables Allow publish in the plugin settings. The onboarding instructions and GPT/Claude guidance also reflect whether publishing is enabled.
The /logs endpoint is restricted by the log access settings. This is intentional. A dedicated Editor account can still create/edit content, but cannot access operational audit data unless that access is enabled.
Yes, by default plugin REST endpoints (including the OpenAPI and MCP endpoints) require HTTPS. A development-only setting can allow HTTP if needed on a local/dev environment.
External bearer-token validation uses a short cache to reduce remote validation traffic. The cache TTL is configurable in settings (External token cache (seconds)), so revoked tokens are typically rejected after that cache window expires.
Yes. You can create the dedicated user and create the Application Password directly from the onboarding page. A profile link is still provided for later review/revocation.
No CRM ticket-management code is bundled in this plugin. It provides generic hooks that let other plugins register their own AI tools. Live Support Tickets is a separate WordPress.org plugin; if it or another installed plugin registers tools through the documented hooks, those tools are available according to that plugin's own settings and permissions.
Posts and pages by default (both enabled). Includes explicitly enabled public custom post types in the Content settings tab. Non-public/system types are excluded. Developers can extend tool behavior with hooks such as vwsm_allowed_content_types, vwsm_mcp_extra_tools, vwsm_mcp_dispatch_tool, vwsm_openapi_components, and vwsm_openapi_document.
No. You need to use ChatGPT, Claude, Codex, or another compatible external AI application. This plugin only provides REST endpoints, an MCP endpoint, and onboarding for those external AI applications.
Yes. Once you set up and authorize the connector in Claude.ai on desktop, it is automatically available in the Claude iOS and Android mobile apps — no additional setup is needed.
Consult VideoWhisper for assistance, reports or feature suggestions.
Please report security bugs found in the source code of the plugin through the Patchstack Vulnerability Disclosure Program. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.
[vwsm_user_connect]; it is included in that user's site context and is never shared with other site users.featured_media support to create and update content contracts. Omit it to preserve the current image or pass 0 to clear it explicitly.[vwsm_user_connect] shortcode. It explains that users can connect ChatGPT, Claude, Codex, or another compatible AI chat app or agent to manage enabled site features, including supported content editing, through normal prompts.action attempts to override the route tool.available_tools and available_action_modules for the current site settings and authenticated userget_current_screen() instead of filter_input() which could return null on some server configurations