Skip to content

MyListing MCP

MyListing MCP adds MyListing-specific tools to Angie by Elementor, allowing it to inspect and manage supported parts of a MyListing website through conversation.

Download MyListing MCP 0.2.0

MyListing MCP gives Angie reviewed tools for tasks including:

  • reading and updating supported MyListing Elementor widgets and page settings;
  • creating and configuring listing types, including fields, Search Forms, Single Page tabs and blocks, Preview Cards, packages, reviews, and expiry settings;
  • managing listings, listing taxonomies, and terms;
  • viewing listing claims, reports, listing statistics, and Search Index diagnostics;
  • reading and updating supported Theme Tools settings, including Map Services, Social Login, Direct Messages, User Roles, and Preview Cards; and
  • generating supported MyListing shortcodes.

The integration does not expose every WordPress or MyListing setting. It limits Angie to reviewed fields and operations, hides sensitive values where supported, and requires confirmation for high-impact changes.

MyListing MCP 0.2.0 requires:

WordPress recognizes Angie and Elementor as plugin dependencies. The MyListing theme must be installed and active separately.

  1. Install and activate the MyListing theme, Elementor, and Angie.
  2. Download the MyListing MCP ZIP file using the button above. Keep the file compressed.
  3. In wp-admin, go to Plugins → Add New Plugin → Upload Plugin.
  4. Select mylisting-mcp-0.2.0.zip, then choose Install Now.
  5. When installation finishes, choose Activate Plugin.
  6. Open Angie and ask it to inspect or update a supported part of your MyListing website.

MyListing MCP does not add a separate settings screen. Once the required components are active, it registers its tools with Angie automatically.

Users must have permission to use Angie before MyListing MCP loads its integration. Each tool also checks the relevant WordPress capability. For example, administrative Theme Tools, Search Index, and User Roles operations require administrative access, while listing and page operations check whether the current user can edit the requested content.

Some changes require an explicit confirmation before the tool applies them. If Angie reports that an operation is forbidden, unavailable, or awaiting confirmation, do not try to bypass the message. Confirm that the signed-in user has the appropriate WordPress role and review the requested change.

MyListing MCP does not independently contact an external server. It registers local tools and makes authenticated, same-origin requests to the WordPress site. Angie is an external AI service operated by Elementor, and an Elementor account is required to connect it. Plan limits or credits may apply.

When you ask Angie to use MyListing MCP, the prompt, tool inputs, and tool results are processed through Angie’s service. Depending on the requested operation, that data can include selected WordPress, MyListing, and Elementor information such as listing and term details, supported settings, page and widget settings, diagnostics, validation errors, and requested changes.

Only use Angie with information you are authorized to process. Before enabling it on a production site, review Angie AI for WordPress, the Angie Terms & Conditions, and the Elementor Privacy Policy.

Download the current ZIP from this page, then go to Plugins → Add New Plugin → Upload Plugin and upload it. When WordPress detects the existing installation, choose Replace current with uploaded. Back up the site before updating and confirm that MyListing, Elementor, Angie, WordPress, and PHP still meet the release requirements.

If MyListing MCP cannot be activated or its tools do not appear in Angie:

  • confirm that WordPress 6.9 or later and PHP 8.0 or later are in use;
  • confirm that the MyListing theme, Elementor, Angie, and MyListing MCP are all active;
  • sign in with a user who can use Angie and has permission to manage the requested content;
  • reload Angie and the current wp-admin or Elementor screen after activation;
  • clear page, object, and CDN caches after updating the plugin; and
  • remember that unsupported settings and operations are intentionally not registered as tools.

If a tool can read a value but cannot change it, review the user’s WordPress capabilities and check whether Angie is waiting for confirmation.

  • Fixed MyListing tools not appearing in Angie after recent Angie updates.
  • Prevented duplicate tool registration when the plugin script loads more than once.
  • Added clearer error messages for incompatible Angie SDK configurations.
  • Updated the Angie SDK from 1.5.2 to 1.7.7.
  • Added automated checks for registration compatibility and availability of all 102 tools.
  • Initial release.