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.

Matt Wiebe

MW Local AI Connector provides WordPress AI connectors for:
<ul>
<li>Local AI: connect WordPress to a self-hosted OpenAI-compatible inference proxy on your own machine.</li>
<li>Actual Computer: connect WordPress to the fixed Actual Computer API endpoint with your API key.</li>
</ul>
The plugin integrates with the WordPress Connectors screen and provides a dedicated settings experience for each connector.
See MW Local AI Connector in action:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/T3yfTrcpxS8?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
This plugin is an independent project by Matt Wiebe and is not affiliated with, endorsed by, or sponsored by Actual Computer, Tailscale, Ollama, LM Studio, or any other third-party service it can be configured to talk to.
<h3>External services</h3>
This plugin can connect to a user-controlled Local AI proxy and to the Actual Computer API. Connections only happen after you explicitly configure the matching connector in the WordPress admin and either save it or trigger an AI request through the WordPress AI Client.
<h4>Local AI proxy (user-controlled)</h4>
The Local AI connector sends requests to the OpenAI-compatible endpoint URL that you enter on its settings page. This endpoint is intended to point at a proxy you run on your own machine (for example, in front of Ollama, llama.cpp, LM Studio, vLLM, or multiple local providers at once).
<ul>
<li>What it sends: the prompts, messages, provider-prefixed model selection, and any other AI parameters supplied by callers of the WordPress AI Client. If you configure an API key, it also sends that key as a <code>Bearer</code> token so the proxy can authenticate the request. It also calls <code>/v1/models</code> on this endpoint to populate the model selector in settings.</li>
<li>When it sends: when an admin saves connection details (model list refresh) and whenever WordPress generates a response through this connector.</li>
<li>Where it sends: the endpoint URL you configure on the Local AI settings screen. By default no endpoint is configured and no requests are made.</li>
<li>Because the endpoint is one you supply, this plugin cannot link a generic terms of service or privacy policy on your behalf — the applicable terms are those of whatever software and network operator is running at that URL. If you expose the proxy through Tailscale Funnel, Tailscale’s terms and privacy policy are available at <a href="https://tailscale.com/terms" rel="nofollow ugc">https://tailscale.com/terms</a> and <a href="https://tailscale.com/privacy-policy" rel="nofollow ugc">https://tailscale.com/privacy-policy</a>. If you expose it through Cloudflare Tunnel, Cloudflare’s terms and privacy policy apply.</li>
</ul>
<h4>Actual Computer API</h4>
The Actual Computer connector sends requests to the fixed base URL <code>https://api.actual.inc/v1</code>, operated by Actual Computer.
<ul>
<li>What it sends: the prompts, messages, model selection, and any other AI parameters supplied by callers of the WordPress AI Client, plus the bearer API key you enter on the settings page. It also calls <code>/v1/models</code> to populate the model selector.</li>
<li>When it sends: when an admin saves connection details (model list refresh) and whenever WordPress generates a response through this connector.</li>
<li>Where it sends: <code>https://api.actual.inc/v1</code>.</li>
<li>Service provider: Actual Computer. Terms of service: <a href="https://actual.inc/terms" rel="nofollow ugc">https://actual.inc/terms</a>. Privacy policy: <a href="https://actual.inc/privacy" rel="nofollow ugc">https://actual.inc/privacy</a>.</li>
</ul>
If you do not configure either connector, this plugin makes no outbound network requests.

MW Local AI Connector

Route WordPress AI requests either to models running on your own machine or to an Actual Computer endpoint.

Ultimate AI Connector for Compatible Endpoints vs MW Local AI Connector