AI Provider Connectors
AI Provider Connectors extends the WordPress AI Client and the core Connectors screen (Settings → Connectors) with four features: 11 ready-to-use AI providers. Connector cards for OpenRouter, Mistral AI, Cohere, Groq, xAI (Grok), DeepSeek, Perplexity, Together AI, Fireworks AI, Hugging Face and Repl
About this tool.
AI Provider Connectors extends the WordPress AI Client and the core Connectors screen (Settings → Connectors) with four features:
- 11 ready-to-use AI providers. Connector cards for OpenRouter, Mistral AI, Cohere, Groq, xAI (Grok), DeepSeek, Perplexity, Together AI, Fireworks AI, Hugging Face and Replicate. Paste an API key, save it, and every feature that uses the WordPress AI Client (such as the AI plugin’s excerpt and summary tools) can route through that provider — exactly like the built-in Anthropic, OpenAI and Google providers.
- Test Connection button. A “Test Connection” button next to the “Connected” badge — and inside the expanded edit panel — for every supported provider. Clicking it re-validates the stored API key against the provider’s live API and shows the result in a tooltip.
- Custom providers. Add up to five OpenAI-compatible endpoints of your own — a hosted API that is not bundled, or a local model server such as Ollama, LM Studio or vLLM — and they behave exactly like the bundled ones.
- AI Providers dashboard. A Settings → AI Providers screen where you switch providers on or off, see at a glance which ones are connected, run connection tests, manage custom providers, and drag providers into the order the AI Client should try them. When a feature needs an AI provider, the first connected provider in your list that supports the task is used.
Bundled providers
- OpenRouter
- Mistral AI
- Cohere
- Groq
- xAI (Grok)
- DeepSeek
- Perplexity
- Together AI
- Fireworks AI
- Hugging Face
- Replicate
Already supported by Test Connection
- Anthropic, OpenAI, Google — when their respective AI Provider plugins are active.
Non-AI connectors (such as Akismet) are not live-tested because they require provider-specific verification flows.