10up

Fueled

This plugin provides <a href="https://ollama.com/" rel="nofollow ugc">Ollama</a> integration for the WordPress AI Client. It lets WordPress sites use large language models running locally or on a remote Ollama instance for text and image generation and other AI capabilities.
Ollama exposes an <a href="https://ollama.com/blog/openai-compatibility" rel="nofollow ugc">OpenAI-compatible API</a>, and this provider uses that API to communicate with any model you have pulled into Ollama (Llama, Mistral, Gemma, Phi, and many more).
Features:
<ul>
<li>Text generation with any Ollama model</li>
<li>Image generation with supported models</li>
<li>Automatic model discovery from your Ollama instance</li>
<li>Function calling support</li>
<li>Structured output (JSON mode) support</li>
<li>Settings page for host URL and seeing available models</li>
<li>Works without an API key for local instances</li>
</ul>
Requirements:
<ul>
<li>PHP 7.4 or higher</li>
<li>WordPress 7.0 or higher</li>
<li>Ollama running locally or on a remote server (like Ollama Cloud)</li>
</ul>

AI Provider for Ollama


I have tried in my local machines and it works very well with ollama


Works very well with ollama

Ollama provider for the WordPress AI Client.

Andrei Lupu

AI Provider for Osaurus wires the <a href="https://osaurus.ai" rel="nofollow ugc">Osaurus</a> local LLM runtime into the WordPress AI Client that ships with WordPress 7.0.
After activation, any plugin that calls <code>wp_ai_client_prompt()</code> (Gutenberg AI features, official provider plugins, third-party code) can route prompts to Osaurus running on the same machine. Prompts never leave the local network.
<h4>Why use it</h4>
<ul>
<li>Privacy first — prompts stay on your machine, no third-party API receives the data.</li>
<li>Zero cost — no API keys, no metered requests.</li>
<li>Fast — MLX-backed inference on Apple Silicon.</li>
<li>OpenAI-compatible wire format — streaming, tool calls, JSON output, and chat history work out of the box.</li>
</ul>
<h4>Capabilities</h4>
<ul>
<li>Text generation</li>
<li>Chat history</li>
<li>Function / tool calls</li>
<li>Structured JSON output</li>
<li>Streaming</li>
</ul>
Image generation, embeddings, and text-to-speech are not supported because Osaurus does not currently expose those endpoints. Pair this plugin with an image-capable provider such as the official AI Provider for OpenAI when you need images.
<h4>How it works</h4>
The plugin registers a provider with <code>AiClient::defaultRegistry()</code> and points it at the Osaurus HTTP server. Because Osaurus speaks the OpenAI Chat Completions wire format, the implementation extends the SDK’s OpenAI-compatible base classes — so capabilities like streaming and tool calling flow through automatically.
<h4>Configuration</h4>
The plugin resolves the Osaurus base URL in this order (first match wins):
<ol>
<li><code>OSAURUS_BASE_URL</code> PHP constant defined in <code>wp-config.php</code>.</li>
<li><code>osaurus_ai_connector_base_url</code> option, settable from Settings → Connectors in wp-admin.</li>
<li>Default: <code>http://127.0.0.1:1337/v1</code> (works out of the box for bare-metal WordPress on the same Mac as Osaurus; Docker setups must override).</li>
</ol>
<h4>Pick the right URL for your setup</h4>
WordPress can run in many places — the right base URL depends on how it reaches your Mac, where Osaurus is listening.
<ul>
<li>Bare-metal WordPress on the same Mac (MAMP, Laravel Valet, Local, WordPress Studio, native PHP): 
 http://127.0.0.1:1337/v1 (this is the default — no configuration needed)</li>
<li>Docker-based WordPress on the same Mac (DDEV, Lando, Docker Desktop): 
 http://host.docker.internal:1337/v1</li>
<li>WordPress on a different machine on your LAN, Osaurus on your Mac: 
 http://:1337/v1 — make sure Osaurus is bound to a non-loopback interface and your firewall allows port 1337.</li>
<li>Remote Osaurus you operate (e.g. a Mac mini on Tailscale, a colocated server): 
 http://:1337/v1 or <code>https://...</code> if you front it with TLS.</li>
</ul>
The fastest way to confirm a URL works from the WordPress host: run <code>curl <base-url>/models</code> from the same shell environment WordPress runs in. A JSON list back means the connector will work.
Osaurus project home: <a href="https://osaurus.ai" rel="nofollow ugc">osaurus.ai</a> 
Osaurus documentation: <a href="https://docs.osaurus.ai" rel="nofollow ugc">docs.osaurus.ai</a>
<h3>External services</h3>
This plugin connects to an Osaurus HTTP server — a local LLM runtime that you install and run yourself on the same machine as WordPress (or on a host you operate). The plugin is useless without it: every text-generation request from the WordPress AI Client is routed to this server.
Service: Osaurus (self-hosted, local LLM runtime)
Osaurus is an open-source Apple Silicon LLM runtime that exposes an OpenAI-compatible HTTP API. It is installed and operated by the same person running WordPress — there is no third-party service operator. This plugin forwards prompts to it so WordPress can perform text generation, chat, tool calls, and structured JSON output without sending data to any cloud provider.
Project homepage and download (<code>osaurus.ai</code>): https://osaurus.ai 
Project documentation (<code>docs.osaurus.ai</code>): https://docs.osaurus.ai
These URLs are referenced in the plugin’s admin UI as documentation/download links only; the plugin does not make HTTP requests to <code>osaurus.ai</code> or <code>docs.osaurus.ai</code>.
Hosts the plugin actually contacts at runtime
The plugin sends HTTP requests only to the host and port resolved (in order) from:
<ol>
<li>The <code>OSAURUS_BASE_URL</code> PHP constant (if defined in <code>wp-config.php</code>).</li>
<li>The <code>osaurus_ai_connector_base_url</code> WordPress option (set from Settings → Connectors).</li>
<li>The built-in default <code>http://127.0.0.1:1337/v1</code>.</li>
</ol>
Two host targets are referenced by name in the plugin code as quick-pick presets and as the default:
<ul>
<li><code>127.0.0.1:1337</code> — loopback on the same machine as WordPress (default). Used by bare-metal installs (Studio, MAMP, Valet, Local, native PHP).</li>
<li><code>host.docker.internal:1337</code> — Docker’s hostname for the host machine. Used by Docker-based WordPress (DDEV, Lando, Docker Desktop). Resolved by Docker, not by a public DNS server.</li>
</ul>
If the user configures a different URL, the plugin only contacts that URL. The plugin never contacts any third-party endpoint operated by the plugin author, the Osaurus project, or any other party.
What data is sent and when
<ul>
<li>When any plugin (including WordPress core) calls <code>wp_ai_client_prompt()</code> and routes through Osaurus, the plugin sends a <code>POST</code> to <code>{base_url}/chat/completions</code> with: the prompt text, the conversation history you supplied, the model ID, sampling parameters (temperature, top_p, max tokens, etc.), and any tool / function declarations or JSON schemas you supplied.</li>
<li>When an admin opens Settings → Connectors, the plugin sends a <code>GET {base_url}/models</code> to populate the model picker and a <code>GET {base_root}/health</code> to display a connection status indicator. Both run only for users with <code>manage_options</code> and are triggered by user actions in wp-admin.</li>
<li>No telemetry, analytics, or background requests are sent.</li>
</ul>
Terms of service and privacy policy
Osaurus is open-source software you self-host. There is no third-party service operator collecting your data. See the project pages linked above for the project’s terms and source. If you point the plugin at a remote Osaurus server operated by someone else (for example, a Mac mini you reach over Tailscale), the operator of that server is the data recipient and is governed by whatever terms you have with them.

AI Provider for Osaurus

Registers Osaurus, a local Apple Silicon LLM runtime, as a provider for the WordPress AI Client.

AI Provider for Ollama vs AI Provider for Osaurus