WordPress Is AI Native. Alpha Release. Free LTDs for the extended Fluent Community.

Hi FluentNauts — J here.

In plain English: I built an AI control layer for WordPress and Fluent Plugins due ot our business needs. Others are doing the same, in many different ways.

Helmar Rudolph kindly made me aware my original post was confusing so here is hopefully a more clear update.

You can read Helmars post here

You'll notice in the comments this is not appreciated by all community users, sorry about that.

A system that lets any AI — Claude, GPT, Gemini, whatever you bring — operate WordPress as an operating system. Through structured, permission-gated, schema-validated abilities. With your Fluent suite as native operations.

The Alpha launches in this community today.

What this is as simply as I can at the moment.

Abilities for Fluent — first-party WordPress Abilities API translator for the entire Fluent ecosystem. CRM, Community, Forms, Boards, Booking, Cart, Affiliate, Support, SMTP, Auth, Snippets, Messaging. Conditional module loading. Everything you already run — now operable by AI through conversation.

Open Source GLP2

On our production site — running the full Fluent stack alongside SureCart, Presto Player, Astra, Spectra — the AI discovers +1,600 abilities across 42 modules at boot. FluentCRM alone exposes 318. FluentBoards 198. FluentCart 158. FluentBooking 115. FluentCommunity 109.

The point is not the counts, it is the capacity to operate Wordpress with AI. And Fluent.
Which is a challenge in itself. AI makes mistake, so do humans.

Abilities for AI — Native WordPress abilities for AI agents. Content, blocks, themes, plugins, users, filesystem, cron, multisite. 111+ structured operations across WordPress core. Powered by the official WordPress 6.9 Abilities API.

Open Source GLP2

The MCP Bridge — One MCP to Rule Your WordPress World. Local Node.js server. Multi-site. Multi-client. OS-keychain key storage. We run 3 multisites and 7 single sites in parallel through ONE bridge. Same auth model. Same boot sequence. Different abilities loaded per site.

Open Source GLP2

The MCP Adapter — Upload, activate, and your WordPress abilities become MCP tools. OAuth 2.1. Scoped tokens. Three-bucket redaction. Layered permissions.

Open Source GLP2

Ask your AI

The repos are public. The architecture is documented. Ask your AI to read them, do a safety and security check, and help you install:

• Bridge → https://github.com/Wicked-Evolutions/abilities-mcp
• Adapter → https://github.com/Wicked-Evolutions/abilities-mcp-adapter
• Abilities for AI → https://github.com/Wicked-Evolutions/abilities-for-ai
• Abilities for Fluent → https://github.com/Wicked-Evolutions/abilities-for-fluent-plugins

Trinity overview on our prototype site we are building now only with AI into a Gutenberg site → https://wicked-evolutions.github.io/wickedevolutions-prototypes/marketing-alpha/Trinity%20Hub.html

Sign up for Alpha access (coupon codes + instructions in 1 email) →
https://wicked-evolutions.github.io/wickedevolutions-prototypes/marketing-alpha/Get%20Alpha%20Access.html

Two effects that fall out of this architecture

The Knowledge Layer. Every AI session can leave structured intelligence behind — when you run the protocol.

The Boot Sequence loads the site's identity, history, and operating directives at session start. The End Session Protocol — adapted in conversation between you and the AI — captures what worked, what didn't, and any SKILL or agent definition worth keeping.

Example: you build a full funnel — automations, tags, email sequences, landing page. It works. You and the AI run the End Session Protocol together. The AI writes the SKILL that codifies the pattern, logs the session, captures the observations. Next session, that SKILL is part of the site's institutional knowledge. The next AI session boots into it.

The site gets smarter. Not the AI — the site.
Through deliberate practice, not automatic capture.

The Bridge Effect. WordPress is a shared runtime. Plugins live in the same PHP process, the same database, the same hook system. They share post types, post meta, taxonomies, users, options. The abilities architecture treats this as a feature, not a limitation.

Every plugin that builds on native WordPress structures becomes operable through abilities — not because we wrote a specific integration, but because the WordPress core CPT system itself is the integration. The ability surface extends automatically.

What this opens:

• AI can operate plugins that have no AI integration of their own
• Composability across plugins through shared WordPress state — no HTTP, no round-trips, just in-process function calls
• A new plugin category: micro-plugins that ARE abilities — no admin UI, no settings page, just composable operations
• The need for plugin-specific AI integrations dissolves; abilities become the universal AI interface to anything WordPress already addresses natively

This is structural, not configurational. Install a CPT-based plugin and its content is in the ability surface from the first call.

The Alpha Offer

Free LTDs for the Fluent Community and beyond.
200 LTD Coupons per Pro gated plugin.

Both unlock Pro for life with auto-updates.

The MCP Bridge and MCP Adapter are free GLP2.

Each plugin has these options:

• 1 Site LTD
• 2 Sites LTD
• 1 Multisite LTD

Use the minimum you need. Share equally. If that were our approach to life, Earth and others — the world would be in a much better shape than it is.

Sign up, you'll get one email with the Coupon Codes and links to where you can get them.
You can of course get them in the repos as well, which then is without the PRO gated write, update and delete abilities.

A short personal note

I'm J — Uppsala, Sweden. Solo founder. I don't read or write code. I design systems, plant things, build structures.

I needed full sovereignty over data, infrastructure and user relationships to build Wicked Evolutions — an open source social innovation startup reimagining systemic living through holistic approaches and life-centric technology. Basically, we aim to build geodomestic domes.

WordPress was the only honest answer. The Fluent ecosystem was the operating layer on top.

And when WordPress 6.9 shipped the Abilities API — wp_register_ability() — on February 27th, 2026, everything changed.

Honest disclaimer

These tools are exceptionally powerful. The checkout includes this:

"I acknowledge that using this product is my own free will and responsibility. It is a powerful tool. I'll use it with knowledge and wisdom."

You're getting the keys to a turbo-injected way to operate WordPress with AI. You'll need to learn how to drive.

Alpha is not "we'll see if this works." Alpha is "this works at scale across our entire operation, and we need use case variations we cannot generate alone."

We don't track our users. We don't advertise. We create and share products on one premise: if it's useful, valuable, and worthy of recommending — that's all that's needed.

If it is not good enough, end of story.

You and we bet on the right stack. Things will not be the same tomorrow.

J and the Claude AI Team