Site Agent

• Fixed OAuth connections are bound to the approving site, and concurrent token use cannot restore revoked credentials or overwrite a completed refresh.
• Fixed Partial autosaves preserve omitted fields; registered metadata honors native permissions and schemas; save hooks see final metadata and terms.
• Fixed File mutations and fatal-change rollbacks preserve concurrent edits, including must-use plugin moves.
• Fixed Captured output remains valid UTF-8 and preserves JSON object shapes; imported media and new terms retain literal backslashes.
• Fixed Failed package builds preserve previous ZIPs and checksums; HTTP mutation checks require a verified disposable fixture and recognize all bundled skills.

• Added Bundled workflow guides for MailerHive, Core Support, FluentCart, GT Extensions for FluentCart, Stackless for WooCommerce and Page Blocks Builder (PBB).
• Added site-context reports plugin workflow integrations, installed versions, active state and associated skills. Existing plugin-provided skills continue to supply their detailed commands.
• Updated MCP server instructions, the settings skills panel and companion guidance direct clients to the matching plugin workflows. All developer operations retain their existing opt-ins.

• Fixed OAuth sign-in failed with "Sorry, you are not allowed to access this page" in clients that add their parameters to the authorization address with a second ?, such as Grok. The authorization endpoint is now /wp-json/site-agent/v1/oauth/authorize, which has no query string and forwards to the consent screen.
• The old consent address repairs such requests, so clients that saved it earlier also connect.

• OAuth connections are on by default. Sites that never changed the setting get them as soon as Site Agent is enabled; a site that turned them off keeps its choice.
• Tools → Site Agent leads with connecting through OAuth and moves Application Passwords to a "not recommended" section with a warning. It also warns when OAuth is off, when URL authentication is on, and when Application Passwords made tool calls in the last 30 days.
• site-context reports how the connection authenticated. For an Application Password or an authenticated URL it carries a warning that agents pass on, asking the user to reconnect with OAuth.
• Tools → Site Agent lists the plugins that give agents their own skill (GT Extensions for FluentCart, GT Page Blocks Builder and GT Link Manager) and shows which are active on the site.
• Fixed list-skills showed plugin skill descriptions with their YAML quotes.

• New opt-in OAuth 2.1 connections. Turn on "OAuth connections" in Tools → Site Agent, then add the endpoint to an OAuth-capable client (Claude, ChatGPT and others) with no credentials. The client finds the sign-in through the endpoint's 401 response, registers itself, and sends you to a WordPress consent screen where you allow or deny it and pick the tool groups it may use. PKCE (S256) is required.
• OAuth clients get one-hour access tokens and rotating refresh tokens that end after 30 days without use. Only token hashes are stored, tokens authenticate only the MCP endpoint, reusing a rotated refresh token ends the connection, and connections stop when the approving account loses administrator rights. Revoke connections in Tools → Site Agent; audit history shows OAuth calls with the client name.
• Site Agent uses its own issuer, /wp-json/site-agent/v1/oauth, so it never takes over the site-root OAuth discovery documents that another plugin's OAuth server may serve (Rank Math's MCP server does). Each registered client is stored separately.
• Plugins can add read-only skills to list-skills and get-skill with the site_agent_skills filter. GT Extensions for FluentCart 2.8.3 uses it for its gtfc-invoice and gtfc-quote skills.
• Application Passwords in a header or the authenticated URL keep working unchanged.

• Bundle read-only builder skills for Gutenberg, GenerateBlocks, Elementor, Bricks and Divi, with list-skills and get-skill tools, active builders in site-context and the storing builder in get-content.
• Add an opt-in Bricks tools group that serves Bricks 2.4+ abilities on Site Agent's endpoint: Bricks' fast-path tools under their own names, bricks-abilities and run-bricks-ability, with per-password limits, audit history and a PHP execution requirement for Bricks' PHP ability.
• Refuse Elementor, Bricks and Divi layout meta in content writes, because raw writes skip each builder's validation and cache refresh.
• Return the text of the user's autosave from get-content on request, and whether it is newer than the post, so staged edits can be verified and chained.
• Refuse to stage edits to templates and template parts, which core cannot autosave by post ID, with a clear error instead of a REST failure.
• Detect Bricks layouts without an editor mode, GenerateBlocks Pro blocks and GenerateBlocks global styles and conditions.
• Fix the documented default page size of list-terms.

Validation: 59 WordPress integration tests / 383 assertions on PHP 8.3 and 8.5 locally and on the CI matrix, 9 converter tests, PHP syntax and coding standards, runtime and translation freshness, an HTTP MCP smoke test on disposable WordPress including a real fatal-change rollback, and both release ZIPs.

The companion archive is separate from the installable WordPress ZIP. Site Agent does not implement OAuth.

• PHP file writes, moves and deletes are syntax- and compile-checked, then the site is loaded with WordPress's edit-scrape check and a change that causes a fatal error is reverted.
• Tool errors include the real message and line. PHP execution rejects exit and die and reports wp_die(), indirect exits and fatal errors as tool errors.
• Edits to published, private or scheduled posts are saved as autosaves for review unless a status is passed. Scheduling requires a future date. Titles keep tag-like text and percent sequences.
• Content writes accept terms, featured images, slugs, publish dates and SEO meta. New tools list terms, import media with alt text, update media, and create, delete or move source files; must-use plugins are reachable and credential files are blocked by name.
• Each Application Password can be limited to some tool groups. The audit history records targets, the password used and denied calls. Diagnostics and a Test connection button explain connection failures.
• URL credentials are removed before dispatch, WP-CLI @aliases are rejected, and SITE_AGENT_ALLOW_EXECUTION=false blocks source editing, PHP and WP-CLI.
• Updates use WordPress's Update URI hook, cache failed checks, and keep validated metadata when the store is unreachable during an upgrade. Signed-package verification ships without an enforcing key.

Adds inline documentation to Tools > Site Agent for connecting with an authenticated MCP URL. The guide covers enabling URL authentication, creating a dedicated Application Password, generating and copying the endpoint, credential privacy, revocation, and client compatibility. It shows a site-specific placeholder URL without displaying real credentials.

Validation: 33 WordPress integration tests / 144 assertions, 7 converter tests, PHP syntax and coding standards, runtime and translation freshness, disposable WordPress rendering, and both release ZIPs.

The companion archive is separate from the installable WordPress ZIP. Site Agent does not implement OAuth. ChatGPT web compatibility with credential-bearing URLs has not been verified.

Enable URL authentication under Tools > Site Agent, save, then use the converter's new Copy authenticated endpoint button. The URL's auth query parameter contains Base64-encoded username and Application Password credentials. Standard and URL-safe Base64 are accepted; the copy action handles URL encoding and existing plain-permalink query parameters.

Authentication uses WordPress's native Application Password validator on every request. Administrator and enabled-tool checks remain enforced; account passwords, invalid/revoked credentials, conflicting identities and unrelated REST routes are rejected. The mode defaults off, respects emergency disable and HTTPS requirements, and marks MCP responses private/no-store.

Base64 is reversible. Credential-bearing URLs may appear in browser history, proxy/server logs or client configuration. Use a dedicated, revocable Application Password and keep the complete URL private. The client must support Streamable HTTP/MCP and preserve the query on each request. This is not an OAuth implementation or a guarantee of compatibility with every client.

Validation: 33 WordPress integration tests / 144 assertions, 7 converter tests, real headerless local HTTP initialization and tool discovery, route isolation, invalid-credential rejection, cache headers, session termination, coding standards and package checks.

Adds the optional Site Agent companion package, with WordPress workflow instructions, the approved icon and a credential-free MCP connection. The companion covers site inspection, raw-content audits, draft preparation, hash-checked edits and the developer tools enabled on the connected WordPress site.

Two separate ZIPs are provided:

Both companion manifests now use version 0.1.3. The compatibility manifest points to the included mcp.json; the standalone ZIP includes the complete GPL license. Packaging validation is part of CI.

Authentication still requires a compatible private connection using a WordPress Application Password and Basic Authorization header. This release does not add OAuth or claim authenticated ChatGPT web connectivity. Existing WordPress functionality, runtime dependencies and access controls are unchanged.

Validation: 24 WordPress integration tests / 106 assertions, 6 converter tests, PHP/JavaScript syntax, coding standards, translation and generated-runtime freshness, companion metadata/reference checks and ZIP verification.

• site-agent-0.1.3.zip: installable WordPress plugin, also delivered through FluentCart automatic updates.
• site-agent-companion-0.1.3.zip: companion package for compatible ChatGPT/Codex hosts. Do not upload this ZIP to WordPress.

Conversion stays in the browser. The helper accepts grouped Application Passwords and UTF-8 usernames, masks generated tokens and clears sensitive values when inputs change or the page is left. Site Agent does not submit or store converter credentials.

Validation: 24 WordPress integration tests with 106 assertions; 6 converter tests; JavaScript syntax, WordPress coding standards, PHP lint, translation freshness and package checks. Rendered-browser checks covered exact encoding, masking, copy controls and clearing. The official MCP runtime pin and access settings are unchanged.

Access starts disabled. Tool groups are independent opt-ins; developer execution is full-privilege access and is not sandboxed.

This public release adds free FluentCart update-license activation, encrypted site-bound credentials, protected package downloads, fresh download URLs for single/bulk upgrades, and extracted plugin identity checks. Licensing controls automatic updates only; all functionality remains available without activation.

The bundled official WordPress MCP Adapter is the upcoming 0.7.0 prerelease at a pinned source commit, with PHP MCP Schema 0.2.0. No Novamira application code, assets or dependencies are included.

Requires WordPress 6.9+ and PHP 8.0+. PHP 8.0, 8.3 and 8.5 CI passed, including 24 integration tests and 106 assertions. Use the complete release ZIP below; it includes the scoped official runtime.

Product and free update license: https://gauravtiwari.org/product/site-agent/

• Initial independently implemented WordPress MCP developer plugin.
• Separate opt-ins for content writes, source inspection, source editing, PHP, and WP-CLI.
• Native WordPress authentication, private abilities, strict schemas, and scoped official MCP runtime.
• File conflict and PHP syntax checks, metadata-only audit history, and emergency disable.