VideoWhisper Site Manager for ChatGPT, Claude, Codex
| 开发者 | videowhisper |
|---|---|
| 更新时间 | 2026年7月1日 16:34 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- A secure REST layer for content operations (list, read, create, update, revert, reset)
- An MCP (Model Context Protocol) endpoint for Claude.ai, Claude Desktop, Claude CLI, Claude mobile apps, and Codex MCP clients
- A generated OpenAPI schema URL for GPT Actions import
- Guided onboarding with copy/paste values for ChatGPT Builder, Claude connector setup, and Codex MCP setup
- Turnkey OAuth onboarding for shared GPT / shared MCP workflows through a compatible Relay & OAuth Server
- WordPress Application Password onboarding for direct site-owned integrations
- Frontend user connection shortcode support for connected account workflows
- Safety controls: HTTPS enforcement, draft-first behavior, publish gating, read/write rate limiting, write quotas, IP allowlists, audit logs
- Extension points through WordPress hooks for custom authentication, tools, settings, content types, and admin UI additions
- Site owners who want to draft, edit, or review WordPress content by chat
- Teams using a dedicated WordPress user (recommended: Editor) for AI-assisted publishing workflows
- Mobile workflows: configure on desktop, use the GPT or Claude connector on phone/tablet
- Developer workflows where Codex can use MCP tools to inspect and update WordPress content
- Turnkey OAuth - recommended for most sites. 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.
- Install and activate VideoWhisper Site Manager.
- Open VideoWhisper Site Manager > Onboarding.
- Create (or link) a dedicated WordPress user (recommended role: Editor).
- Choose Turnkey OAuth for a shared GPT workflow, or create an Application Password from the onboarding page for a direct site-owned GPT.
- In ChatGPT Builder (desktop), create a Custom GPT and import the plugin OpenAPI schema URL.
- Use the provided copy/paste values for Configure, Actions, authentication, and privacy policy fields.
- Test on desktop, then use the same GPT on mobile.
/wp-json/videowhisper-site-manager/v1/mcp.
Claude.ai (web):
- Go to
claude.ai/customize/connectors. - Click the + button in the Connectors sidebar → Add custom connector.
- Set a name and paste the MCP endpoint URL.
- Authorize via Turnkey OAuth when connected to a compatible Relay & OAuth Server, or use an Application Password for direct setup.
- The connector also works in the Claude mobile apps (iOS and Android) and desktop once authorized.
claude mcp add --transport http "YourSiteName" "https://yoursite.com/wp-json/videowhisper-site-manager/v1/mcp"
Automatic OAuth authorization requires a compatible Relay & OAuth Server. Without that connection, use WordPress Application Passwords over HTTPS.
Connecting Codex (MCP)
The onboarding flow includes Codex setup values for both direct and Turnkey MCP architectures. Codex can connect to the same Streamable HTTP MCP endpoint at /wp-json/videowhisper-site-manager/v1/mcp.
- Open VideoWhisper Site Manager > Onboarding and enable Codex in the AI Tools selection step.
- Choose Turnkey OAuth for shared relay access, or Application Passwords for direct site-owned MCP access.
- Copy the generated Codex
config.tomlblock or OAuth login command from the Codex onboarding tab. - Restart or reload Codex MCP settings, then use
/mcpin Codex to confirm the WordPress MCP server is active.
安装:
- Upload the
videowhisper-site-managerplugin folder to/wp-content/plugins/, or install it via the WordPress Plugins screen. - Activate the plugin through the "Plugins" screen in WordPress.
- Open VideoWhisper Site Manager > Onboarding (you will also see an admin reminder notice until setup is complete).
- Create or link a dedicated WordPress user (recommended role: Editor).
- Choose Turnkey OAuth or create an Application Password directly from the onboarding page.
- For ChatGPT: open ChatGPT Builder on desktop and follow the provided step-by-step instructions. Import the OpenAPI schema from the URL shown in onboarding.
- For Claude: copy the MCP endpoint URL from the onboarding page and follow the Claude.ai, Desktop, or CLI setup instructions shown there.
- For Codex: copy the Codex MCP configuration or OAuth login command from the Codex onboarding tab, then verify the server with
/mcp.
屏幕截图:
常见问题:
Does this plugin store an OpenAI or Anthropic API key?
No. This plugin does not store or use any AI provider API keys.
How does authentication work?
The plugin supports 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.
Can the API publish posts immediately?
Not by default. Publishing 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.
Why does ChatGPT, Claude, or Codex get a 403 on logs?
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.
Does the plugin require HTTPS?
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.
How quickly are revoked external OAuth bearer tokens rejected?
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.
Can I set up everything from the plugin without visiting Users > Profile?
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.
Does the free plugin manage CRM support tickets?
No CRM ticket-management code is bundled in this free plugin. The free plugin provides generic hooks that let other plugins register their own AI tools. Live Support Tickets is a separate free 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.
What content types are supported?
Posts and pages by default (both enabled). Admins can enable or disable each in the Content settings tab. Developers can extend supported content types and 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.
Does it include an AI chat interface inside WordPress?
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.
Does the Claude connector work on mobile?
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.
Where do I report security bugs found in this plugin?
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.
更新日志:
- Removed bundled Live Support Tickets CRM implementation from the free plugin; plugin-specific tools now belong in the extending plugin or add-on that registers them through hooks.
- Added explicit REST permission callbacks for the shared MCP endpoint and OpenAPI action bridge.
- Rejected action bridge requests where a body
actionattempts to override the route tool. - Added plain-language external service disclosures with Terms of Use and Privacy Policy links.
- Updated the plugin display name to start with the VideoWhisper brand name.
- Moved screenshot assets to the WordPress.org SVN assets directory.
- Kept frontend and admin JavaScript/CSS loaded through WordPress enqueue APIs.
- Fixed Stable tag and version metadata for WordPress.org packaging.
- Added translator context comments and tightened review-tool findings.
- Added a dynamic agent guide endpoint and MCP guide resources generated from the shared AI action registry
- Site context now includes
available_toolsandavailable_action_modulesfor the current site settings and authenticated user - Maintenance release that refreshes plugin version metadata and rebuilds the installable distribution package without development files or docs
- Added Codex onboarding and MCP setup guidance alongside ChatGPT and Claude
- Tightened default rate limits to 10 reads/minute, 5 writes/minute, and 30 writes/hour
- Site context and rate-limit rejections now expose current rate-limit details for AI tools
- Updated FansPaysite support wording for theme-specific shortcode styling
- Maintenance release for the current Turnkey OAuth and shared GPT onboarding flow
- Refined release metadata and packaging for the latest Site Manager distribution build
- Turnkey OAuth now reads shared ChatGPT and shared Claude MCP details from the connected Site Manager Server instead of relying on client-side local settings
- Turnkey onboarding links and activation guidance now surface server-provided shared GPT state more consistently
- Added VideoWhisper top admin-bar integration with Site Manager shortcuts
- Updated shared VideoWhisper contact/admin-bar links to use consult.videowhisper.com
- Added: MCP GET endpoint with SSE support per MCP Streamable HTTP transport spec (2025-03-26) — required for Claude.ai, Claude Desktop, and Claude CLI to connect
- Added: Claude Desktop and Claude CLI setup instructions in the onboarding panel (Claude.ai / Desktop / CLI tabs)
- Added: Note that Claude.ai connector also works in Claude mobile apps (iOS and Android)
- Fixed: Onboarding notice now correctly detects the onboarding page using
get_current_screen()instead offilter_input()which could return null on some server configurations
- Fixed: Moved inline JavaScript on the onboarding page to an enqueued external file using wp_enqueue_script() and wp_localize_script()
- Fixed: REST permission callback for /content endpoint now checks the post-type-specific capability (e.g. edit_pages for pages) instead of always checking edit_posts
- Added admin Logs page in wp-admin
- Added configurable audit log retention with daily cleanup
- Simplified onboarding with ChatGPT/Claude tabs
- Updated ChatGPT action setup guidance and sharing safety notes
- Moved advanced options to extension hooks and add-on integration points
- Added/expanded extension hooks documentation for third-party add-ons
- Policy/readiness cleanup for WordPress.org checks
- Initial release
- Direct Mode REST endpoints for content, settings, logs, and OpenAPI
- ChatGPT / GPT Actions onboarding with generated OpenAPI schema URL
- One-click dedicated user + Application Password onboarding helpers
- GPT Builder step-by-step setup instructions with copy/paste values
- HTTPS enforcement for plugin endpoints (with development override)
- Draft-first workflow with optional publish gate
- Audit logging and admin settings controls