Custom development
AI agent integration for WordPress (Abilities API & MCP)
Let an assistant read your store, and where you allow it act on your store, through a defined set of abilities instead of a scraped page.
Scoped and quoted per project. Fixed quote before any work starts. No hourly billing.
A WordPress Abilities API MCP integration gives an AI agent a list of things it is allowed to do on your store, instead of leaving it to guess from your HTML. The Abilities API is the registry: each ability has a name, a JSON schema for its input and output, and a permission callback that decides who may run it. An MCP server exposes that registry to assistants that speak Model Context Protocol.
What the assistant sees is a menu — find product, check stock, look up order status — and nothing else. We decide with you which abilities exist, who may call them and what they return. A support assistant might read order status and never touch prices. An internal agent might create draft products but never publish one. Every call is written to a log, so “what did the agent actually do” has an answer you can read.
Typical build
- A plugin registering your store’s abilities, each with an input and output JSON schema and its own permission callback.
- An MCP endpoint exposing those abilities, authenticated with application passwords or scoped tokens — never your admin session, never a shared key.
- Read abilities and write abilities kept separate, so an agent can be granted one without the other.
- An audit log of every call: caller, arguments, result, timestamp — queryable from wp-admin.
- A written list of what the agent can and cannot do, for you and for whoever answers your support mail.
Good fit if…
- You want ChatGPT, Claude or an internal assistant to answer questions from live stock and order data rather than a cached page.
- You are building a support or operations agent and it needs to act on the store, not only talk about it.
- You want agent access with real permissions and a log, instead of an API key that can do everything.
How it connects to AI visibility
Schema and merchant feeds tell an assistant what you sell before anyone asks. Abilities let it check the answer at the moment of asking — this price, this stock level, this customer’s order. They work in the same direction: the AI Visibility Setup makes your catalogue readable to crawlers, and an abilities layer makes it answerable to agents, from the same source of truth.
FAQ
Straight answers to the questions store owners ask
Is the Abilities API stable enough to build on?
The surface is small — register an ability, declare its schema, declare who may run it — which is what makes it reasonable to build on. We keep our registration layer thin so that if the API changes, the change lands in one file rather than spreading through your integration.
Can an agent place orders?
Technically yes, and we usually advise against it at first. Start read-only, watch the log for a few weeks, then decide which write abilities have earned their place. Write abilities can also require a human confirmation step.
Do I need to run a separate MCP server?
No. It runs inside your WordPress install, on your hosting, behind the same TLS as the rest of the site. There is no extra service to pay for and no copy of your data somewhere else.
What happens when the assistant gets it wrong?
Abilities are schema-validated, so malformed calls fail before they reach your data. Every call is logged with its arguments, so a mistake can be traced, explained and reversed rather than argued about.
Custom development
Tell us what should happen automatically.
Describe the job someone does by hand, or the system your store cannot talk to. You will get a reply from the engineer who would build it, within one working day.
Describe your automation