by
axtolab
0 (0 reviews)
Axtolab AI Connector
Let AI agents read, draft, edit, and publish WordPress with per-connection permissions, consent gates, and Roll Back.
Axtolab AI Connector ranks #21,739 among WordPress.org plugins with 40+ active installations, and was last updated Jun 19, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 7.0.6 (Current: 7.1.2)
v1.0.3
Current Version v1.0.3
Updated 3 months ago
Last Update on 19 Jun, 2026
Refreshed 8 hours ago
Last Refreshed on
Downloads -24.6% this week
Rank
#21,739
—
No change
Active Installs
40+
+60%
KW Avg Position
132
59 better
Downloads
872
+10 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 50
40+
50+
1,741
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 4 more installs to reach 50+
Rank Changes
Current
#21,739
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.3
- Last Updated
- Jun 19, 2026
- Requires WP
- 6.2+
- Tested Up To
- 7.0.6
- PHP Version
- 7.4 or higher
- Author
- axtolab
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Axtolab AI Connector
Any MCP-compatible AI agent, including Claude (via Claude Desktop or Claude Code), ChatGPT (via MCP plugins), and custom agents built with the MCP SDK.
Yes. The AI Connector supports full content workflows including creating, editing, publishing, and scheduling content. No limits on publishing.
The plugin itself does not send your content to an Axtolab-hosted service. Content stays between your WordPress site and the MCP client/server you choose to run. Optional stock-photo and AI-image tools connect to their configured provider APIs only when you explicitly use those tools — see the External Services section below.
Yes. Single-site and multisite installations are supported by the free core.
The plugin supports two authentication methods: WordPress Application Passwords (for Desktop AI clients) and OAuth 2.1 with PKCE (for Web AI clients like ChatGPT and Claude Web). Each MCP connection authenticates as a WordPress user that the administrator chose during setup — either their own admin account (simple) or a dedicated WP user they created themselves (recommended for production sites). The plugin never creates WordPress users or roles. Each tool call runs with that user's WordPress capabilities, layered with the per-connection capability set (read / publish / trash / media / SEO / etc.) the administrator chose for the connection. Both layers must allow an action for it to succeed.
Each method has a specific scope. Pick the one that matches what your client needs to do: Application Password (HTTP Basic Auth) — works against every plugin REST endpoint (/site-info, /content/*, /media/*, /yoast/*, /abilities/*, etc.). This is available for custom clients and local MCP clients that need direct REST access. The connection wizard packages the username + Application Password into a single wmcp1_ token you can paste into Claude Desktop / Claude Code without copying credentials manually. OAuth 2.1 with PKCE — OAuth-issued access tokens are sent as standard Authorization: Bearer <token> headers and are scoped to the MCP-over-HTTP transport only (/wp-json/axtolab-ai-connector/v1/mcp). They do not authenticate the ordinary REST API surface. This scope split is intentional: OAuth is the path remote/web MCP clients (ChatGPT, Claude Web) use to access the JSON-RPC tool surface, while ordinary REST is reserved for trusted local MCP servers using Application Passwords. If you need OAuth-issued credentials to call ordinary REST endpoints directly, contact support — we can extend the scope on request once your use case is documented.
This is informational, not an error — your AI Connector is working correctly. The plugin tries to publish OAuth discovery metadata at three locations: the standard RFC 8414/9728 paths (/.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server), an issuer-relative path used by ChatGPT (/wp-json/axtolab-ai-connector/v1/.well-known/...), and direct REST endpoints (/wp-json/axtolab-ai-connector/v1/oauth/metadata/...). Real-world MCP clients (Claude Desktop, ChatGPT, Claude Web) use the latter two paths and do not need the host-root paths to work. If your site is on a host where nginx sits in front of Apache or LiteSpeed (most managed WordPress hosts including SiteGround, WP Engine, Kinsta, Cloudways), nginx serves /.well-known/* paths directly and never forwards them to PHP. The plugin's .htaccess rewrite is therefore bypassed at the nginx layer — that's what the warning detects. MCP client connectivity is unaffected. If you do want full RFC 8414/9728 compliance (e.g. you're integrating with strict OAuth validators), ask your host to add the following nginx configuration block — typically inserted before any catch-all .well-known location and before the index.php fallback: location ~ ^/\.well-known/oauth-(protected-resource|authorization-server)$ { try_files $uri /index.php$is_args$args; } After the host applies this and reloads nginx, the warning will clear within 6 hours (or sooner if you visit the AI Connector admin page).
No. Claude, ChatGPT, OpenAI, and WordPress are trademarks of their respective owners. Axtolab AI Connector is not affiliated with, endorsed by, or sponsored by Anthropic, OpenAI, or the WordPress Foundation.