How to connect an AI assistant to wpDataTables

You connect an AI assistant to wpDataTables by generating a WordPress application password and pointing your MCP client at the wpDataTables endpoint. Once connected, the assistant discovers the plugin’s tools and can build tables and charts for you from your own machine.

There is nothing to enable inside wpDataTables; the MCP server registers itself as soon as the site meets the requirements, so all of the setup happens in your WordPress profile and in the client. For background on the technology behind the connection, refer to the AI Assistant integration documentation.

What do I need before I start?

Have these ready before you begin.

• WordPress 6.9 or newer, with wpDataTables installed and active; the Abilities API ships with WordPress 6.9, and on older versions the MCP server does not register
• A site administrator account, since wpDataTables checks the manage_options capability on every request
• An MCP-compatible AI client such as Claude Desktop, Claude Code, or Cursor
• Node.js installed on the computer running the client, which provides the npx command used below
• The full URL of the WordPress site where wpDataTables is installed
• HTTPS on the site for production use, since WordPress requires it for application passwords on non-local sites

How do I create a WordPress application password?

The application password is created from the profile of the admin account that will authorize the connection. We recommend adding a new admin user, but you can use your own admin user as well.

Go to WP Admin → Users → Add User, set the username (this is what you’ll use for the connection), then scroll down to Application Passwords. Enter a recognizable name like wpDataTables MCP, and click Add New Application Password.

Copy the value right away; WordPress only shows it once. Keeping the spaces inside it is fine. For the username in your client config, use the WordPress login name shown at the top of the profile, not the label you gave the password, and not your email address.

How do I add the wpDataTables server to my MCP client?

Most clients speak stdio locally while WordPress speaks HTTP, so the connection runs through the @automattic/mcp-wordpress-remote proxy. In every client, you point that proxy at the wpDataTables endpoint, https://YOUR-SITE/wp-json/mcp/wpdatatables-mcp-server and pass your username and application password as environment variables.

Replace YOUR-SITE with your real domain and the credentials with the ones from the previous step, and keep the rest of the path exactly as shown.

How do I configure Claude Desktop?

Add the following block to claude_desktop_config.json. If the file already contains other MCP servers, add only the wpdatatables entry inside the existing mcpServers object instead of replacing the whole file.

{
  "mcpServers": {
    "wpdatatables": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
      "env": {
        "WP_API_URL": "https://YOUR-SITE/wp-json/mcp/wpdatatables-mcp-server",
        "WP_API_USERNAME": "your-wp-login-username",
        "WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx",
        "OAUTH_ENABLED": "false"
      }
    }
  }
}

How do I configure Claude Code?

Run the following from the command line, and the server is registered without editing a configuration file by hand.

claude mcp add wpdatatables \
  --env WP_API_URL=https://YOUR-SITE/wp-json/mcp/wpdatatables-mcp-server \
  --env WP_API_USERNAME=your-wp-login-username \
  --env WP_API_PASSWORD='your-application-password' \
  --env OAUTH_ENABLED=false \
  -- npx -y @automattic/mcp-wordpress-remote@latest

How do I configure Cursor?

Add the same mcpServers block shown for Claude Desktop under Cursor’s MCP settings, either in Cursor → Settings → MCP or in a project .cursor/mcp.json file, depending on your setup. The structure matches Claude Desktop’s format exactly, so the block can be copied across without changes.

How do I confirm the connection works?

Fully quit and reopen your client so the proxy starts with the new environment variables, then check that the wpDataTables server shows as connected and lists its tools. You should see 23 entries, named after the actions they perform, such as wpdatatables-list-tables, wpdatatables-get-system-info, wpdatatables-create-simple-table, and wpdatatables-create-chart.

Ask the assistant a read-only question first, such as to list the tables on your site or to report the plugin’s system info; if it returns data that matches your wpDataTables → Browse screen, the endpoint, credentials, and tool discovery are all working. Only test an action that creates something after the read-only request has succeeded.

How does the assistant build a table for me?

You ask in plain language, for example, “create a wpDataTable from this sales CSV”, and the assistant chains the actions itself. It typically starts by checking system info to learn your license tier and available connections, uploads the data file to the media library, and then either creates a live table that reads the file on every render or imports it once into MySQL as an editable table.

For database data, it inspects the schema first, listing and describing database tables, before creating a table from a SELECT query. The result comes back as a table ID and a shortcode, and the table appears under wpDataTables → Browse exactly as if you had built it in the wizard. wpDataTables also ships a built-in workflow prompt for the file upload path, so a client that supports MCP prompts can follow the recommended sequence without you spelling it out.

Why don’t I see wpDataTables tools in my client?

An empty tool list or a server error almost always comes down to one of the causes below.

• The URL is wrong; it must end in /wp-json/mcp/wpdatatables-mcp-server, not just /wp-json/
• The account is not a site administrator; every wpDataTables action requires the manage_options capability, including the read-only ones
• The username is an email address instead of the WordPress login name, or the application password was mistyped
• The configuration contains the regular WordPress login password instead of an application password, which returns an incorrect_password error
• WordPress is older than 6.9, so the Abilities API is unavailable and the MCP server never registers; check WP Admin for a wpDataTables notice saying so
• The client cannot find npx, which means Node.js is missing or was installed after the client was last started
• A plain 403 Forbidden page can mean the web server is stripping the Authorization header before the request reaches WordPress; ask your host to confirm that the header is passed through

What should I keep in mind about AI-assisted tables?

Connecting an AI assistant to wpDataTables takes three things: an administrator application password, the endpoint at /wp-json/mcp/wpdatatables-mcp-server, and an MCP client configured to reach it through the WordPress remote proxy. Everything the assistant can then do runs through the same permission and license checks as the plugin’s own interface, so it is a second way into wpDataTables rather than a way around it.

• Start with a read-only request, such as listing tables, before asking the assistant to create anything.
• Keep each request to one clear task; chained requests that create a table, restyle it, and build a chart in one go are less reliable than separate prompts.
• Review tables and charts the assistant creates, since anything you did not specify falls back to default settings.
• Give each application password a clear name so you can revoke the right one later without guessing.
• Run the site over HTTPS in production so application passwords work and stay protected in transit.
• Don’t connect with an account you would not trust with full administrator access, since the assistant inherits it entirely.
• Don’t share the application password or commit it to a repository.
• Don’t point the proxy at the generic WordPress MCP endpoint; use the wpDataTables URL so you get the right tools.
• Don’t expect the assistant to delete a table or clean up after itself, since the integration has no delete action.