MCP Abilities - Store Locator lets an AI assistant keep your existing location data current

When a WordPress site already relies on Store Locator, an AI assistant can work with the records behind its visitor-facing map without creating a second directory.
Download MCP Abilities - Store Locator
Art Deco Store Locator machine with a map, location pins, record drawers, and category controls

Keep the locator’s data native

Keep the records behind the map in place

Store Locator keeps location content in its own posts and metadata, including address, contact, location, and category information.

MCP Abilities – Store Locator gives an AI assistant an authenticated WordPress path to inspect and maintain that native surface.

Its maintained templates preserve the Store Locator shortcode, map, search, AJAX result list, labels, and cache behavior.

The add-on leaves Elementor cards, static listings, and duplicate store records out of page content.

What an AI assistant can maintain

Use the operation that matches the change

Check the current locator before a change, then use the supported operation for presentation, records, categories, or cache maintenance.

Start with the current state

Read Store Locator availability, current settings, installed templates, and published store count before changing anything. Then update supported settings with Store Locator-aware validation.

Set the locator presentation

Configure translated Store Locator permalink bases and language-specific frontend labels. Choose which source-language store navigation links and labels appear in selected frontend languages, then set the active search template from the installed templates.

Maintain native store records

List stores, inspect one native record’s address, contact, and location metadata, create a supported store record, or update supported store fields and categories. Store Locator remains the system that owns those records.

Use the categories that exist

List the native Store Locator category terms before reviewing or assigning categories to store records. Organization stays tied to the terms already available in the locator.

Clear Store Locator autoload transients

After a supported data, settings, or template change, clear Store Locator autoload transients when cache maintenance is needed.

Match the request to the surface

Decide whether the change fits this ability set

The add-on handles supported Store Locator maintenance through authenticated operations; unrelated WordPress edits and unexposed actions need a different workflow.

Supported writes are explicit

Settings updates use Store Locator-aware validation, while store updates are limited to supported fields and category assignments. Inspect the current state first so the request can name an existing setting, record, category, or installed template.

Store deletion is not exposed

The available store operations list, inspect, create, and update records. They do not include deleting a store, so plan removal through a separate authorized workflow.

A layout request can stay at template level

For a request such as putting location listings into columns, inspect the installed templates, activate the appropriate maintained template, clear Store Locator autoload transients, and verify the rendered locator page. The store records do not need to be rewritten for that presentation change.

Before you use it

What the setup needs

These named dependencies provide the runtime, authenticated ability transport, and native locator that owns the data.

Required: 6.9 or later

WordPress 6.9+
Provides the WordPress runtime and native Abilities API used by the add-on.

Required: 8.0 or later

PHP 8.0+
Provides the PHP runtime for the plugin.

Required

WordPress MCP Adapter
Transports registered WordPress abilities to an authenticated MCP client.

Required

MCP Expose Abilities
Makes the registered abilities available through the Devenia MCP surface.

Required

WP Store Locator
Owns the store records, metadata, categories, settings, templates, map, search, and AJAX result state used by these operations.

Choose the native path

Download the AI path for your existing locator

Choose this download when a WordPress site already uses Store Locator and the next supported change should stay with its native records. The ZIP gives an AI assistant a path to inspect and maintain that data while the locator’s own map and search continue to use it.
Download MCP Abilities – Store Locator