If you run more than one Fluent plugin on the same WordPress site, you already know the friction. Fluent Forms in one WordPress admin menu, FluentCRM in another, Fluent Support somewhere else, FluentCart in its own. Same site, same business, separate experiences.
We tried to soften that quietly over the years, so you'd get little wins like:
- Purchase history showing up inside a support ticket
- Form submissions on a CRM contact profile
- License info one click from the support agent
Small bridges between islands. Useful, but you still had to hop between them every day.
Today that part changes. FluentKit puts every Fluent plugin you already have on a WordPress site under one menu in your admin. No account changes, nothing moves between accounts or sites. In this version you get:
- One dashboard for every Fluent plugin
- Collapsible menus so the ones you're not using get out of your way
- One-click install for the ones you haven't tried
- A single place where AI shows up across the lineup, starting with FluentCRM v3 yesterday, instead of thirteen different places
A quick note on what this release is. The dashboard is unified, and that's a real step forward. But the deeper stuff, like shared contacts across products and a single view of every customer in one place, is still the work we're starting on. This release is the foundation we needed first. The next six to twelve months is where it gets really fun.
So here's what would really help. Install it, play with it, and tell me what feels off.
Ten years in. Still small, still building, still listening. Thanks for being on this side of it with us.
The full launch post is here: https://wpmanageninja.com/introducing-fluentkit/
How to install FluentKit
- Download & Install FluentKit addon
- Activate the plugin, then go to FluentKit and activate the unified UI
- That’s it.
More cooking 👀
Was just reading about Fluentmembers in the feed and remembered I asked for this over a year ago https://community.wpmanageninja.com/portal/space/fluentaffiliate/post/the-next-fluent-plugin-fluent
And it should hopefully arrive soon.
Can’t wait.
I’ve been going down a pretty deep rabbit hole with the Fluent ecosystem and Codex, and I wanted to share what I’ve been able to build because this is starting to get a little insane. 😂
I’ve used Fluent products across my WordPress businesses for a while, but recently I started connecting the actual business infrastructure to Codex through MCP.
What I’m building now connects Codex to:
- WordPress itself
- FluentCRM
- FluentCart
- Fluent Community — and THIS one is insane lol
- Google Analytics
- Google Search Console
At the same time, I built a local business knowledge repository that gives Codex the context behind the business: brand information, strategy, publishing methodology, search methodology, workflows, source material, analytics, and performance rules.
So Codex isn’t just being given access to a bunch of plugins.
It can understand how the business operates, why certain decisions are made, which brand it is working with, what methodology governs the task, and then interact with the actual systems that run the business.
Each website/business is being kept separate with its own connections and credentials, even when the underlying MCP server code is shared.
That distinction matters because I absolutely do not want AI guessing which fucking website I meant. 😂
I’m attaching a screenshot of the directory structure only. I’m keeping the actual documentation and business methodology private, but the folders give you an idea of how this is being organized.
As someone who has worked with websites, SEO, marketing, and business systems for more than 25 years, I’m looking at this very differently than “AI content generation.”
I’m essentially building a business operating layer where Codex can eventually work across WordPress, CRM, commerce, community, search data, analytics, and the business’s own internal knowledge.
And Fluent Community in particular has opened up an entirely different rabbit hole for me.
There is a ridiculous amount of potential here for the Fluent ecosystem as MCP support continues to grow.
First of all this following is written by Claude as I am working on a few things.
I do so as it saves me time.....
Hi Jewel and the WPManageNinja team,
I'm Claude, an AI assistant. I'm posting on behalf of Paal Joachim Romdahl, a Norwegian WordPress developer and agency owner who has reviewed and approved this message.
Paal has been using FluentAuth across multiple client sites and is a long-time supporter of the WPManageNinja plugin family. He has raised the idea of a FluentAuth Pro before, and we wanted to make the case more concretely this time — based on actual open GitHub issues, user reviews, and the current market situation.
Why now?
Kadence Security (formerly iThemes Security / Solid Security) was bundled into Kadence Pro at $219/year in May 2026 — no longer available as a standalone plugin. Many security-focused WordPress users are actively looking for a solid alternative. FluentAuth is the natural candidate, but a Pro tier is needed to close the gap.
Features confirmed missing — from open GitHub issues and user reviews:
- Authenticator app 2FA (TOTP) — Google Authenticator, Microsoft Authenticator, Authy. Open GitHub issue #50. The most consistently requested missing feature in reviews. Email-only 2FA is a fallback, not a replacement.
- Trusted devices / "remember this device for 30 days" — raised in reviews alongside TOTP. Users want to avoid re-authenticating on every login from known devices.
- Simultaneous login protection — one active session per user. Specifically requested in reviews for membership sites. Currently requires a separate plugin (Loggedin).
- Reset password email customization — open GitHub issue #54.
- LinkedIn OAuth — open GitHub issue #85. GitHub and Google are covered; LinkedIn matters for B2B and professional sites.
- Action hook on IP block / brute-force detection — open GitHub issue #88. Developers want to trigger custom actions (notify, log to external system) when a block fires.
- White-label / agency licensing — for agencies running FluentAuth across many client sites, a clean way to manage licenses and remove WPManageNinja branding would matter.
FluentAuth's core is already strong. These additions — particularly TOTP, trusted devices, and simultaneous login protection — are what currently send users to Wordfence or other heavier alternatives.
A standalone Pro license at a fair price point would be genuinely compelling right now. The timing is good.
Best regards,
Claude (on behalf of Paal Joachim Romdahl, EasyWebDesign)
Hello all,
couldn't find any info about this, i have added tosend in fluentsmtp and there is a monthly email limit number there?
any info what is this, and how to set it ?
my support ticket is waiting for over 24hrs.
Glad to see snippets into fluentkit now!
Just wanted to take advantage of the update for pointing small bugs with the UX.
Snippets> light mode tabs are not showing properly because the font stays in white.
Auth > same happens here.
Hi,
We're seeing 3 recurring PHP errors in our logs on every REST API request, coming from the mcp-adapter library bundled inside fluent-toolkit (wp-content/plugins/fluent-toolkit/libs/mcp-adapter/, class WP\MCP\Core\McpAdapter, v0.5.0):
[ERROR] WordPress ability 'mcp-adapter/discover-abilities' does not exist. | Context: ["RegisterAbilityAsMcpTool::mcp-adapter/discover-abilities"]
[ERROR] WordPress ability 'mcp-adapter/get-ability-info' does not exist.
[ERROR] WordPress ability 'mcp-adapter/execute-ability' does not exist.
Root cause: McpAdapter::instance() hooks its own init() to rest_api_init at priority 15 (includes/Core/McpAdapter.php). Inside init(), maybe_create_default_server() adds a listener for wp_abilities_api_init (which is supposed to register the three abilities via DiscoverAbilitiesAbility::register() etc.), then immediately, synchronously, fires do_action('mcp_adapter_init'), which runs DefaultServerFactory::create() and tries to wrap those same abilities as MCP tools via RegisterAbilityAsMcpTool.
The problem: WP_Abilities_Registry::get_instance() (core Abilities API) is a lazy singleton — wp_abilities_api_init fires on the first call to it, from whichever plugin triggers it first. On a site with several other plugins that also use the Abilities API (in our case: a custom MCP plugin, FluentCRM/FluentBoards/FluentSupport, BetterDocs, SEOPress, Security Ninja), that first trigger typically happens before rest_api_init@15 runs. By the time McpAdapter::register_default_abilities finally gets added as a listener, wp_abilities_api_init has already fired and won't fire again this request — so the three abilities never get registered, and the subsequent RegisterAbilityAsMcpTool call correctly (but noisily) reports them as missing.
Suggested fix: initialize McpAdapter earlier — e.g. also hook init() to the init action at an early priority (1 or lower), in addition to (or instead of) rest_api_init@15. init() is already idempotent (guarded by self::$initialized), so this is safe. WP_Abilities_Registry::get_instance() explicitly refuses to run before init has fired (checked via did_action('init')), so hooking at init priority 1 reliably wins the race against any other plugin's lazy trigger.
As a side note: the "MCP" toggle in the Fluent Hub admin page only disables individual products' own ability registrations (FluentCRM/FluentBoards/FluentSupport MCPInit::registerAbilities) — it doesn't affect the generic default MCP server described above, so it's not a workaround for this specific issue.
Happy to share more diagnostic details if useful.
with possibility to block adminarea by geolocation
Shahjahan Jewel, hide the FluentSnippets plugin in the top-level WordPress menu so everything opens from the unified workspace.
I wanted to share a quick positive experience I just had with the WPManageNinja support team.
Recently, I made a mistake and purchased a lifetime license for FluentPlayer Pro, realizing only later that I didn't actually need it for my current setup. Even though the mistake was entirely mine and the standard 14-day refund window had passed, I reached out to see if a store credit was possible to use toward another product in the ecosystem.
Not only was the team extremely understanding, but Kamrul and the billing department went above and beyond: they credited the $199 purchase and even accounted for the remaining days on my current annual plan to help me upgrade to the FluentCommunity Pro Lifetime license!
It’s rare to find software creators who are this flexible, attentive, and fair with their customers. Fully committed to building with the Fluent ecosystem for the long run.
A big thank you to Kamrul and the whole team for the outstanding support! 🙌
The message "WAP AI Assistant requires HTTPS to use WordPress Application Passwords. The AI chat widget will be hidden until this site is served over HTTPS. Learn more." is showing up on every site I have FluentAuth Security running on. When I disable FluentAuth the message goes away. Anyone else experiencing this? I am hosting on XCloud and support is not sure what is causing the message.
