Integrations / GeoDirectory
Governed integration
GeoDirectory MCP abilities
4 governed GeoDirectory abilities for AI agents. They appear on your WordPress MCP server only while GeoDirectory is active, and stay off until you enable them. Read and write business and place listings.
Governed exactly like core
These abilities are off until you enable them, capability-checked before every call, and written to the same audit log as everything else. There is no separate trust model for integrations.
Off even when GeoDirectory is active
Every other integration appears as soon as its host plugin is detected, leaving you to enable the individual abilities. This one goes a step further: the whole integration stays off until you switch it on in the Integrations tab, on a site already running GeoDirectory.
- Active only while GeoDirectory is installed and active
- Off by default, enabled one ability at a time
- Capability-gated on every call, discovery and execution separately
- Logged like core, denials included, keys and identifiers, never free-text
How to turn it on
Activate GeoDirectory, then open the Agent Abilities for MCP screen and enable the GeoDirectory abilities you want. Connect your client to the endpoint on the Connection tab. The address below is illustrative; your real one shows there.
The 4 GeoDirectory abilities
Each one is off until you enable it and capability-checked on every call. Open any card to see how it is governed.
Get GeoDirectory listings
Read onlyList GeoDirectory business/place listings (title, status, link). Default-off integration; enable it in the Integrations tab.
View abilityGet a GeoDirectory listing
Read onlyRead one GeoDirectory listing by id, including its address and coordinates. Default-off integration.
View abilityCreate a GeoDirectory listing
Guarded writeCreate a new GeoDirectory business/place listing with a title, content, and optional address/coordinates. Default-off integration.
View abilityUpdate a GeoDirectory listing
Guarded writeUpdate an existing listing's title, content, or address/coordinates. Fields omitted from the call are left untouched. Default-off integration.
View abilityTry it with a prompt
Example requests you could paste to your agent once GeoDirectory abilities are on.
List the published GeoDirectory listings and tell me which ones are missing an address.
Read listing 88 and show me its address and coordinates.
Add a listing for the new bakery on Mill Street with its address.
Fix the phone number and address on listing 88, and leave the rest of the fields as they are.
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Add GeoDirectory, keep the same control.
Every integration ability is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Active only while its host plugin is on, and gated like core.