David Stone

This plugin extends the WordPress AI Client to support any AI service or server that uses the standard chat completions API format (<code>/v1/chat/completions</code> and <code>/v1/models</code> endpoints).
Supported services include:
<ul>
<li>Ollama – Run open-source models (Llama, Mistral, Gemma, etc.) locally on your own hardware.</li>
<li>LM Studio – Desktop application for local LLM inference with a one-click server.</li>
<li>OpenRouter – Unified API providing access to 100+ models from multiple providers.</li>
<li>vLLM – High-throughput inference server for production deployments.</li>
<li>LocalAI – Drop-in replacement for running models locally.</li>
<li>text-generation-webui – Popular web UI with API server mode.</li>
<li>Any compatible endpoint – Works with any server implementing the standard format.</li>
</ul>
Requirements:
<ul>
<li>WordPress 7.0+ – The AI Client SDK is included in core. This plugin works on its own without any additional dependencies.</li>
<li>WordPress 6.9 – Also supported when the Gutenberg plugin (23.0+) is active, which provides the AI Client SDK.</li>
</ul>
Why it matters:
Other AI-powered plugins that use the WordPress AI Client (such as AI Experiments) can automatically discover and use any model you connect through this plugin. Configure your endpoint once and every AI feature on your site can use it.
How it works:
<ol>
<li>Install and activate the plugin.</li>
<li>Go to Settings > Connectors and configure the connector with your endpoint URL (e.g. <code>http://localhost:11434/v1</code> for Ollama).</li>
<li>Optionally provide an API key for services that require authentication.</li>
<li>The plugin registers a provider with the WordPress AI Client and dynamically discovers all available models from your endpoint.</li>
</ol>
The plugin also handles practical concerns like extended HTTP timeouts for slow local inference and non-standard port support.

Ultimate AI Connector for Compatible Endpoints

Connects the WordPress AI Client to Ollama, LM Studio, or any AI endpoint that uses the standard chat completions API format.

Per Søderlind

This plugin registers exo as an AI provider in WordPress 7’s AI Client SDK and Connectors page.
<a href="https://github.com/exo-explore/exo" rel="nofollow ugc">exo</a> connects all your devices into an AI cluster, enabling you to run frontier models locally. It exposes an OpenAI-compatible API that this plugin connects to.
Features:
<ul>
<li>Registers exo as a WordPress AI provider</li>
<li>OpenAI-compatible text generation via exo’s chat completions API</li>
<li>Auto-detect active models from your running exo cluster</li>
<li>Capability detection — displays model capabilities (Text, Code, Thinking, Vision) as badges</li>
<li>“Connect & Detect” / “Save & Re-detect” connector flow</li>
<li>Optional API key authentication with secure storage</li>
<li>Configurable endpoint URL (default: <code>http://localhost:52415</code>)</li>
<li>Settings integrated into WordPress 7’s Connectors page</li>
</ul>
Choosing a Model:
exo exposes every model in its catalog, but only models actively loaded on your cluster will respond. Use “Connect & Detect” on the Connectors page to discover which models are running.
Recommended — Instruct models produce clean, usable output for WordPress AI features (title generation, content suggestions, etc.):
<ul>
<li><code>Llama-3.2-3B-Instruct-8bit</code> — ~3 GB, fast, great for short tasks</li>
<li><code>Meta-Llama-3.1-8B-Instruct-4bit</code> — ~4 GB, good balance of speed and quality</li>
<li><code>Llama-3.3-70B-Instruct-4bit</code> — ~35 GB, best quality, needs a larger cluster</li>
</ul>
Avoid — Reasoning/thinking models (Qwen3.5, DeepSeek, GLM, Nemotron-Nano) spend most tokens on internal chain-of-thought, producing slow responses with minimal visible output.
To load a model: <code>exo run mlx-community/Llama-3.2-3B-Instruct-8bit</code>
Requirements:
<ul>
<li>WordPress 7.0 or later</li>
<li>PHP 8.3 or later</li>
<li>A running exo cluster (see <a href="https://github.com/exo-explore/exo" rel="nofollow ugc">exo documentation</a>)</li>
</ul>
<h3>Configuration</h3>
The plugin can be configured via the Connectors page or environment variables:
<ul>
<li><code>AIPRFOEX_ENDPOINT</code> — exo API endpoint (default: <code>http://localhost:52415</code>)</li>
<li><code>AIPRFOEX_API_KEY</code> — Optional API key for authentication</li>
<li><code>AIPRFOEX_MODEL</code> — Model name to use (auto-detected if empty)</li>
</ul>
You can also define these as constants in <code>wp-config.php</code>.

AI Provider for exo

Connect WordPress to exo — run frontier AI models locally on your device cluster.

Ultimate AI Connector for Compatible Endpoints vs AI Provider for exo