RevUpNow MCP – MCP Server for Claude, ChatGPT, Elementor & AI Agents

Değişiklik Kaydı

1.2.3

• Removed incomplete Beaver Builder snapshot tools from the review package.
• Fixed a health-check warning for the removed support-access scheduler.
• Removed obsolete administrative mode controls and corrected the Guide and setup wizard to describe content-only access.
• Migrated old administrative mode settings to content editing and discarded unsupported scopes.
• Enforced a fixed content-tool manifest and authenticated request context at dispatch.
• Removed legacy Elementor REST routes and the externally initiated customer resync route; Elementor content tools remain on the authenticated MCP endpoint.
• Kept dashboard-only credential and permission management separate from remote content access.

1.2.2

• Remote API-key and OAuth requests have a content-only capability ceiling, including administrator-linked credentials.
• Removed remote site-settings, menu-management, and customer-user listing tools.
• Remote requests cannot manage plugins, themes, users, credentials, site settings, or unfiltered HTML.
• Sanitize nested Elementor content and reject internal configuration post types.
• Load the connected-services panel CSS from a bundled stylesheet.

1.2.1

• Diagnostics/usage reporting is no longer enabled by default: the Welcome wizard’s checkbox starts unchecked,
  and a site where the choice was never made is now treated as not opted in. WooCommerce customer sync and
  aggregate usage reporting likewise stay off after connecting a licence until separately and explicitly
  turned on – connecting alone no longer enables either.
• The Account & Sync panel’s styles are now added with wp_add_inline_style() instead of a raw inline
  tag.
• Fixed two hardcoded /wp-json/ REST paths (license and store-sync connections on local/dev installs) to use
  rest_url() instead, so they respect a site’s own REST URL prefix.
• update_site_settings no longer accepts permalink_structure. Changing the permalink structure rewrites every
  URL on the site, which is a critical/administrative setting rather than the non-sensitive settings (site
  title, tagline, timezone, date/time format) this tool is scoped to; it is no longer reachable remotely.

1.1.0

• Plugin name adjusted to meet WordPress.org’s restricted-term rules.
• Added an optional site connection for aggregate MCP usage reporting and WooCommerce customer contact sync.
• Added explicit disclosure, automatically active post-connection services, manual backfill, disconnect and
  remote customer-data deletion controls.
• Lite MCP functionality no longer has a request cap and remains available without connecting.

1.0.9

• Renamed. The plugin is now RevUpNow MCP, published under the
  revupnow-mcp slug.
• Removed the last unreachable licence surfaces left over from earlier
  builds, so nothing in the package refers to keys, plans or upgrades.
• The plugin file’s direct-access guard now runs before any other code.
• Admin JavaScript is enqueued rather than printed inline.

1.0.8

• Database queries now carry a complete, correctly placed annotation
  explaining that table names come from $wpdb->prefix and never from user
  input, with every value passed as a placeholder.

1.0.7

• Addressed every issue reported by the official Plugin Check tool.
• Security: all output escaped, POST arrays sanitised element by element,
  and database queries annotated so the table-name interpolation is
  reviewable.
• Uses wp_is_writable() rather than is_writable(), which also reports
  correctly on Windows hosts.
• Removed a dead auto-update toggle left over from the licence screen.
• Fixed mixed line endings and a Domain Path header pointing at a folder
  that was not shipped.

1.0.6

• The plugin no longer has any licence, account or connection to an external
  service. It makes no outbound requests at all.
• Removed licence activation, the Licence screen, usage reporting, WooCommerce
  customer sync and the diagnostics opt-in.
• Fixed: the 100-requests-a-day allowance is now actually enforced. A build
  fault meant the counter was read but never incremented, so the limit never
  applied. It is now a self-contained local check with no external dependency.
• Documentation rewritten to match what the plugin does.

1.0.5

• Removed the Plugin URI header, which duplicated the Author URI.

1.0.4

• Corrected readme claims that did not match the shipped build.
• Tested up to WordPress 7.1.

1.0.3

• The setup wizard shows connection settings without requiring anything first.

1.0.2

• Fixed a setup wizard step that could not be completed.

1.0.1

• Fixed: the plugin no longer requires a licence to run.

1.0.0

• First release.