Description
KimaAI brings modern AI features to WordPress by connecting your site to AI providers (like OpenAI) and exposing them through an easy-to-configure chatbot and a growing set of AI tools.
With KimaAI you can:
- Build a customizable chatbot with model/provider selection, content awareness, quick actions, and an optional attention popover.
- Add a vector database search tool and multilingual embeddings to power smarter, language-aware answers.
- Collect chatbot feedback to understand response quality and improve your on-site experience over time.
- Use a setup wizard to get started quickly, plus a settings system designed to be maintainable and extensible.
- Extend KimaAI via developer hooks/filters to register and control custom tools and tool execution.
KimaAI is built to stay flexible: it works for non-technical users who want a powerful chatbot, and it also provides hooks and internal APIs for developers who want to integrate AI deeper into their workflows.
Please make sure to carefully read the Disclaimer before using the plugin, check the KimaAI website for more information. Thank you!
Features
- AI Chatbot: provider/model selection, content awareness, quick actions, and UI customization.
- Setup Wizard: guided first-time configuration.
- Vector Search: vector DB search tool + embeddings to improve answers.
- Multilingual-ready: multilingual embeddings and translatable dynamic settings (Polylang/WPML).
- Feedback: collect user feedback on chatbot responses.
- Developer hooks: register custom tools and control/observe tool calls.
- More features coming soon!
My Vision for AI
AI is incredible, no doubt about it. It’s changing everything—from the way we work to the way we create. But for me, AI isn’t just about churning out endless content or automating everything for the sake of it. I want to see AI being used thoughtfully—as a tool that actually helps people.
I dream of an AI-driven world where creators can focus on their ideas instead of struggling with words, where language barriers don’t hold anyone back, and where tedious work is handled for us so we can spend more time on what really matters—our passions, our families, and just enjoying life.
I’ll always push for AI to be used in a way that empowers rather than overwhelms. Hope you’re with me on this! 💡💙
Disclaimer
KimaAI is a plugin that helps you to connect your websites to AI services. You need your own API keys and must follow the rules set by the AI service you choose. For OpenAI, check their Terms of Service and Privacy Policy. It is also important to check your usage on the OpenAI website for accurate information. Please do so with other services as well.
The developer of KimaAI and related parties are not responsible for any issues or losses caused by using the plugin or AI-generated content. You should talk to a legal expert and follow the laws and regulations of your country. KimaAI does only store data on your own server, and it is your responsibility to keep it safe. KimaAI’s full disclaimer is here.
Screenshots
Installation
- Upload the plugin files to the
/wp-content/plugins/kimaaidirectory, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the ‘Plugins’ screen in WordPress.
- Run the Setup Wizard — it guides you through connecting your AI provider and API key.
- Place the chatbot on your site and start answering visitor questions.
FAQ
-
How do I get an API key?
-
You can get an API key from OpenAI by creating an account on their website. Check the OpenAI website for more information.
-
Yes. Under Chatbot Security you can withhold the chatbot until the visitor accepts it. Pick “WP Consent API” if your banner supports that standard (Complianz, CookieYes, WPConsent and others), or “Script blocking” for banners that block scripts in the browser such as Usercentrics, Cookiebot and Borlabs. Consent gating is off by default.
Reviews
Contributors & Developers
“KimaAI – AI Chatbot & Assistant for WordPress” is open source software. The following people have contributed to this plugin.
Contributors
Translate “KimaAI – AI Chatbot & Assistant for WordPress” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
Unreleased
Added
- Added cookie consent gating for the chatbot, so it can be withheld until the visitor accepts it in your cookie banner. Two modes cover both kinds of consent manager: WP Consent API (Complianz, CookieYes, WPConsent and others report the choice to WordPress) and script blocking (Usercentrics, Cookiebot, Borlabs block in the browser, so the script is marked with the attribute they look for). Consent also gates the visitor-facing REST routes and the session cookie itself, and withdrawing consent clears that cookie — the widget’s own consent notice could not do either. Safe to use behind a full-page cache: the markup is the same for every visitor and the decision is made in the browser. Off by default, so nothing changes until you enable it. The chatbot’s cookie and storage entries are registered with the WP Consent API, so compatible banners can list them without you compiling the list by hand.
1.5.8 – 2026-09-14
Added
- Added a Utility Model dropdown in the chatbot’s advanced settings, replacing the free-text model field, with Reasoning level and Verbosity controls that appear for models that support them. Internal helper calls (query rewriting, groundedness checks) now honor these settings; leave the model on “Default” to keep using the chat model.
- Added an MCP (Model Context Protocol) server so AI agents can observe and diagnose the chatbot over a single authenticated endpoint (
POST /wp-json/kimaai/v1/mcp). Read/diagnose tools cover usage stats, knowledge gaps, feedback, conversations/incidents, eval history, and — for a given query — asking the chatbot, inspecting retrieval, classifying the likely failure, and checking embedding coverage. Access is gated by scoped bearer tokens (wp kimaai mcp token) or WordPress Application Passwords and a newkimaai_mcpcapability; every call is audit-logged, analytics output is PII-redacted by default (raw requires theread:rawscope), and ungrounded answers are recorded for diagnosis. Audit and groundedness rows are kept for 90 days, filterable viakimaai_mcp_log_retention_days. - Added an MCP Server screen under the Integrations settings tab to manage the MCP server without the CLI: it shows the endpoint URL, an enable toggle and environment selector, a copy-paste connection command, and a table to create scoped access tokens (shown once) and revoke them. The endpoint is disabled by default and stays closed until you turn it on.
- Added an OAuth 2.1 authorization server (authorization code + PKCE + Dynamic Client Registration, with discovery metadata and a WordPress-login consent screen) so claude.ai Custom Connectors can connect to the MCP server without a manually-created token.
- Added gated write tools to the MCP server so agents can apply fixes, not just diagnose: change settings (with a preview step and one-command rollback), re-embed content, run the golden-set eval, and capture a fix as a new eval case. Writes require the
writescope and route through the existing safe-write pipeline; settings changes and eval-case additions return a rollback id. - Added a post-type restriction for embedding auto-sync, so auto-embed on first publish and auto re-embed on update only run for the post types you select. Leave every box unchecked to keep embedding all supported post types.
Changed
- Removed AI Presets. Every surface now selects its own AI environment, so the chatbot’s own environment and model drive the chatbot and its internal helper calls, and embedding uses the embedding environment. On upgrade, an install set to “Default (Set AI Presets)” keeps running on the same environment and model, and the embedding selection is carried into the embedding environment; settings you had configured yourself are left untouched.
Developer
- Added real end-to-end coverage for the embedding auto-sync pipeline: tests publish and update real posts, run a real Action Scheduler queue, and assert on real embedding rows.
- CI now runs on demand via the
run-cilabel or a manual dispatch, instead of on every commit and every push to the main branch.
For the full changelog, visit:
https://kimaai.com/changelog/