AI Engine – The Chatbot, AI Framework & MCP for WordPress vs BotCreds Agent Artifacts

AI Engine connects WordPress with AI models. One install, stable connectors for every major AI provider: OpenAI, Anthropic, Google, Mistral, and more. Build intelligent chatbots, generate content, create AI forms, and automate tasks. All from your WordPress dashboard. Please make sure you read the disclaimer. For more information, check the official website of AI Engine. Quick Intro Hello! ☀️ I built AI Engine to bring OpenAI, Anthropic, and other AI models into WordPress. Create chatbots that understand your content, generate posts in your voice, translate instantly, create images, or build custom AI tools. For developers: internal APIs, REST endpoints, function calling, and MCP support. Build AI features, automate workflows, or create SaaS applications on WordPress. Feeling overwhelmed? 🤪 Start simple: Create a chatbot. Then connect Claude Code, Claude, ChatGPT, or OpenClaw through MCP, giving AI direct access to your site. Desktop clients can connect via OAuth: users just paste the MCP URL, sign in to WordPress, and approve. No shared token to manage. Add SEO Engine and watch it manage SEO in ways you never imagined. You can even connect AI Engine to multiple WordPress sites and manage them all through conversation. You’ll be having a blast before you’ve explored everything. You’ll probably spot bits of AI Engine in plenty of other AI plugins, code and UI alike. Flattering, really… or fishy? 🤣 But only AI Engine keeps pushing forward with real care for its community, a drive toward perfection, and the patience to get the details right. Core Modules 🤖 Chatbots Create intelligent chatbots with customizable themes, realtime audio, and multi-file support. Features modular UI Builder, conversation memory, and MacOS-style components. 🎨 Content & Media Generate content, translate text, create images and videos from prompts, and use Copilot in the WordPress editor to correct, enhance, translate, or rewrite text. 📝 AI Forms Build custom AI-powered forms that handle text, images, audio, or file uploads. Create advanced apps with conditional logic. 🧠 Knowledge & Embeddings Create embeddings and build knowledge bases from PDFs. Connect with Pinecone, Chroma, Qdrant, or OpenAI Vector Store for semantic search. 🔧 Function Calling Connect AI to WordPress functions, WooCommerce, appointments, or custom APIs. Let AI interact with your site’s data and services in real-time. 🛡️ Security & Moderation IP banning, word filtering, and content moderation to keep your AI interactions safe. 💡 Advisor AI-powered recommendations and insights to help you set up and optimize your WordPress site. 🔌 Developer Tools Internal APIs, REST endpoints, MCP support, and extensive hooks. Build AI-driven features, automate workflows, or create SaaS applications. 🤖 Chatbots Transform visitor interactions with intelligent, customizable chatbots. Features: Modular UI Builder with containers, headers, footers Customizable themes and MacOS-style components Realtime audio conversations Multi-file upload support Discussion memory and history Cross-site embedding GDPR compliance tools 🎨 Content & Media Create, refine, and visualize content with AI assistance. Copilot (Magic Wand): Correct grammar and spelling Enhance text for readability and quality Make text longer or shorter Translate text and full posts Generate content from scratch Multi-block support in the WordPress editor Image & Video Tools: Create images from text prompts Generate videos with AI (Sora) Edit existing images with AI Vision AI for image analysis Automatic alt text generation 📝 AI Forms Build powerful AI-driven forms and applications. Capabilities: Text, image, audio, and file inputs Conditional logic and validation Custom AI-powered apps Multi-step workflows Result templates 🧠 Knowledge & Embeddings Create intelligent knowledge bases and semantic search. Vector Databases: Chroma, Qdrant, Pinecone OpenAI Vector Store Automatic synchronization Dimension validation Smart Features: PDF import with auto-chunking AI-powered search (Simple, Context-Aware, Smart) Content classification Personalized recommendations 🔧 Developer Tools Extend WordPress with AI capabilities. APIs: Internal API for plugin integration REST API for external applications MCP (Model Context Protocol) support Function calling framework Integration: Works with SEO Engine, Social Engine, Code Engine Media File Renamer support Custom shortcodes and hooks Extensive WordPress filters Resources: Code Examples & Customization MCP (Model Context Protocol) AI Engine turns your WordPress site into an intelligent MCP server. AI agents like ChatGPT, Claude, Claude Code, and OpenClaw can connect directly, browse content, edit posts, manage media, and handle complex tasks through natural conversation. What AI Agents Can Do: Create and edit posts Moderate comments Install and manage plugins Customize themes Check SEO and analytics Manage media files Run SQL queries Manage WooCommerce products, orders, inventory, and customers Handle Polylang translations Setup Guides: General MCP Overview MCP with ChatGPT MCP with Claude MCP with Claude Code Plugin Integration: Other plugins add their features to the MCP system: SEO Engine – Let AI analyze and optimize your content, fix SEO issues, and manage meta data Social Engine – AI can schedule posts, manage social media, and create social content Code Engine – Give AI access to code snippets and custom functions AI Engine can also connect to external MCP servers, extending your chatbots with tools and services beyond WordPress. Pro Features AI Forms: Create dynamic forms that generate answers, images, or files using AI. Embeddings & Vector Databases: Build knowledge bases from your content and PDFs for semantic search. Content-Aware: Let AI use your post and page content as context for smarter responses. Function Calling: Connect AI to WordPress functions, WooCommerce, or any custom API. Cross-Site Chatbots: Embed your chatbots on external websites. Editor Assistant: An AI sidebar in the post editor that can read, rewrite, insert, and rearrange your content blocks through chained function calls. Realtime Audio: Voice-based conversations on OpenAI’s GA Realtime API, with the latest voice reasoning capabilities. Statistics & Usage Control: Track usage, set limits per role, and monitor costs. Extra MCP Tools: Adds plugin, theme, database, Polylang, and WooCommerce management to the MCP server. Priority Support: Get faster help from the Meow Apps team. Why AI Engine? Native to WordPress Built specifically for WordPress with seamless integration. No clunky interfaces, just native WordPress experience. Flexible & Powerful Built-in connectors for OpenAI, Anthropic, Google, xAI (Grok), Mistral, Perplexity, OpenRouter, Replicate, Azure (OpenAI), plus a Custom (OpenAI-compatible) connector for Ollama, LM Studio, vLLM, llama.cpp, LocalAI, or any self-hosted server. Use the models that work best for you. Google (Gemini) runs on the new Interactions API by default, bringing stateful conversations, streaming with a live event log, function calling, and built-in Google Search and Google Maps grounding, with the classic API kept as a one-click fallback. Developer Friendly Clean APIs, extensive hooks, and MCP support. Build custom AI features or entire SaaS applications on WordPress. Real MCP, for Real WordPress You may have heard of MCP Adapter, built by the WordPress team primarily for their WordPress.com hosting service. It’s essentially a thin layer on top of the REST API. AI Engine takes a different approach: its MCP tools are specifically crafted for AI agents, with rich context, smart defaults, and practical actions that go far beyond what a generic REST API wrapper can offer. And it works on any WordPress installation, regardless of your hosting provider. AI Engine also exposes its REST API as MCP tools if you want that, but the dedicated tools are where the real power is. Privacy First IP hashing, GDPR tools, secure file handling, and session-based tracking. You control your data. Constantly Evolving Weekly updates based on real user feedback. We listen, we improve. My Dream for AI I am excited about AI, but I believe we need to use it with intention and clarity. Social media showed us how powerful tools can reshape our lives in ways we never expected, sometimes for the better, sometimes not. I want to avoid repeating those mistakes. AI should help us remove the meaningless, tedious work or enhance the work we enjoy. Modern tools should give us more time for what truly matters: spending beautiful moments with the people we love! 💕 Disclaimer AI Engine 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 AI Engine 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. AI Engine does only store data on your own server, and it is your responsibility to keep it safe. AI Engine’s full disclaimer is here. Compatibility Please be aware that there may be conflicts with certain caching or performance plugins, such as SiteGround Optimizer and Ninja Firewall. To prevent any issues, ensure that AI Engine is excluded from these plugins.

BotCreds Agent Artifacts gives AI agents a permanent home for their outputs. Post a single HTML file to the REST API. The plugin parses it, extracts scripts and styles, saves them as static files, enqueues them properly via WordPress APIs, and serves the result at a clean public URL with strict security headers. No build tools. No infrastructure. One API call. How It Works POST raw HTML to /wp-json/wp/v2/artifacts The plugin extracts and blocks and saves them as static files in wp-content/uploads/artifacts/{id}/ JS and CSS are enqueued via wp_enqueue_script() / wp_enqueue_style() — no inline scripts in rendered output The HTML body is sanitized with wp_kses() and an expanded allowed-tags list (canvas, SVG, inputs, video, audio, data-* attributes) The artifact is served at yourdomain.com/artifacts/{slug}/ with a strict Content Security Policy From the caller’s perspective: POST HTML, get URL. Everything else happens server-side. Features Deployment Single REST API call — no SDK, no library, any HTTP client works Update artifacts in place — POST to /wp-json/wp/v2/artifacts/{id} and the public URL stays the same Optional artifact_description field for internal documentation Head content preservation — tags and other elements from submitted HTML are preserved in output External script support — tags are registered as external dependencies and enqueued alongside local assets Asset cache busting — enqueued files are versioned with filemtime() so browsers fetch updates automatically Clean redeploys — old asset files are deleted before new ones are written Security Content Security Policy on every artifact page — blocks external script injection and cross-origin data exfiltration by default Trusted CDN list out of the box: cdn.jsdelivr.net, unpkg.com, cdnjs.cloudflare.com, esm.sh, cdn.skypack.dev — scripts and styles load from these without any configuration Per-artifact API allowlist — artifacts that call external APIs declare their origins via an HTML pragma comment ( ) or a deploy-time meta field; the plugin adds them to connect-src automatically Additional security headers: X-Content-Type-Options, X-Frame-Options, Referrer-Policy Custom capability type — artifact capabilities are separate from standard post capabilities; only Administrators can create artifacts by default Developer Hooks botcreds_agent_artifacts_csp — filter the full CSP header value for any artifact botcreds_agent_artifacts_allowed_html — filter the wp_kses allowed-tags array botcreds_agent_artifacts_grant_to_role() — helper to grant capabilities to additional roles Custom template — drop single-artifact.php in your active theme to replace the render template Use Cases OpenClaw (AI personal assistant) OpenClaw agents can deploy interactive dashboards, daily digests, data visualizations, and mini-apps in a single tool call. Generate the HTML, POST it, get the URL — no manual steps, no context switching. For artifacts that fetch live data, add a pragma comment to the HTML and the CSP is updated automatically: For recurring reports (daily digests, weekly summaries), store the artifact ID after the first deploy and update in place on subsequent runs. The URL never changes. Claude Code (terminal-based coding agent) Claude Code sessions can invoke a shell deploy script directly after generating output. Add a scripts/deploy-artifact.sh to your project and reference it in your CLAUDE.md — Claude will use it to ship outputs without leaving the terminal. No manual copy-paste, no browser switching. Codex (OpenAI coding agent) Same pattern as Claude Code. Add deployment instructions to your AGENTS.md and Codex can write HTML, call the deploy script, and report the live URL — all in one agent run. GitHub Actions (versioned project) For projects that build a static HTML output — dashboards, reports, documentation, changelogs — a GitHub Actions workflow can deploy to an artifact on every push to main. The artifact ID is stored as a repository variable so the public URL stays stable across all future deploys. Push → build → deploy → done. Example: Deploy via REST API curl -X POST "https://your-site.com/wp-json/wp/v2/artifacts" \ -u "username:application-password" \ -H "Content-Type: application/json" \ -d '{ "title": "My App", "status": "publish", "meta": { "artifact_html": " Hello. ", "artifact_description": "Built by my AI agent" } }' The response link field is the public URL of the deployed artifact. Example: Artifact with Live Data Include the fetch pragma in your HTML — no configuration needed: fetch('https://api.openweathermap.org/data/2.5/weather?q=Denver&appid=YOUR_KEY') .then(r => r.json()) .then(d => document.getElementById('weather').textContent = d.weather[0].description); Example: GitHub Actions Deployment name: Deploy Artifact on: push: branches: [main] jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - run: npm ci && npm run build - name: Deploy to Artifact env: WP_SITE: ${{ secrets.ARTIFACT_WP_SITE }} WP_USER: ${{ secrets.ARTIFACT_WP_USER }} WP_PASS: ${{ secrets.ARTIFACT_WP_PASS }} ARTIFACT_ID: ${{ vars.ARTIFACT_ID }} run: | PAYLOAD=$(jq -n --arg title "My Dashboard" --rawfile html dist/index.html \ '{title: $title, status: "publish", meta: {artifact_html: $html}}') ENDPOINT="$WP_SITE/wp-json/wp/v2/artifacts" [ -n "$ARTIFACT_ID" ] && ENDPOINT="$ENDPOINT/$ARTIFACT_ID" curl -sf -X POST "$ENDPOINT" -u "$WP_USER:$WP_PASS" \ -H "Content-Type: application/json" -d "$PAYLOAD" | jq -r '.link'