How does AI Assistant integration work in wpDataTables

Imagine asking an AI assistant to “show me sales data for Q1” or “create a new table from this dataset,” and having it happen without opening the wpDataTables admin yourself. That’s what wpDataTables’ AI Assistant integration makes possible, built on the WordPress Abilities API and a dedicated MCP adapter endpoint. This article explains what the integration does, what it can’t do, and how its permissions work.

This is not a built-in AI chat interface inside wpDataTables. The integration lets external MCP-compatible AI clients, like Claude Desktop, connect to your site and interact with your tables through standardized, permission-checked actions.

Table of Contents

What is the WordPress Abilities API?

The WordPress Abilities API is a WordPress initiative (bundled in WordPress 6.9 and newer, with a Composer-based fallback for earlier versions) that lets plugins describe their capabilities in a machine-readable way. Instead of an AI system relying on browser automation, wpDataTables registers its core data actions directly in this registry, so compatible AI assistants can discover and call them through a standard interface.

What is the MCP adapter and how does wpDataTables use it?

The MCP adapter bridges the Abilities API with the Model Context Protocol, translating wpDataTables’ registered actions into tools an AI assistant can call. wpDataTables exposes its own endpoint at /wp-json/wpdt-mcp/mcp, which an MCP-compatible client connects to directly.

Which actions can an AI assistant perform?

Once connected, an AI assistant can call the following actions, each mapped to an approved wpDataTables ability:

List tables
Get table data
Create table
Update table
Delete table
List charts
Create chart
Get chart data
Run query (read-only)
Export table data

Only these actions are exposed; no other WordPress or database functionality is reachable through the integration.

Can an AI assistant write data through the Run query action?

No. Run query is enforced as read-only. An assistant can use it to filter or inspect data (for example, “get all rows where status is active”), but it can’t use it to insert, update, or delete rows. Data changes only happen through the dedicated Create table, Update table, and Delete table actions, each of which still goes through normal permission checks.

What permissions does an AI assistant have?

An AI assistant can only do what the authenticated WordPress user connecting it is already allowed to do. All existing wpDataTables permission rules are enforced on every action, so an Editor or Subscriber account cannot use the assistant to create, update, or delete tables even if the assistant tries; those actions stay admin-only. Unauthenticated requests are rejected outright, with no data returned.

Since a connected assistant inherits the full permissions of the account it’s authenticated as, only connect it using an account you’d trust with that same level of direct access.

Does this integration change the table management flow?

No. There are no changes to the existing table management screens, table rendering, or query engine, and there’s no AI chat interface added inside wpDataTables itself. The integration only adds a way for external AI clients to reach the same underlying actions through the Abilities API and MCP adapter.

What do I need to use this integration?

You need WordPress 5.3 or newer (the Abilities API is bundled via Composer as a fallback on versions before 6.9) and an MCP-compatible AI client, such as Claude Desktop, connected to your site’s /wp-json/wpdt-mcp/mcp endpoint using an authenticated WordPress account.