Three-month batch sync from internal repo (~80 commits) covering Tracks F.5a, F.7e, F.8, F.17, F.18, F.X. WordPress media pipeline - Pillow-based optimization, AI image generation (OpenAI / Stability / Replicate / Google Nano Banana / OpenRouter), chunked + resumable uploads, bulk delete/reassign, idempotent retries. Capability discovery (F.7e) - Per-site credential probe + adapters for WordPress / WooCommerce / Gitea, tier-fit unions granted ∪ roles, capability badge UI with HTMX partial re-check, install hint in every companion-unreachable error. Companion plugin overhaul - Renamed wordpress-plugin/airano-mcp-seo-bridge → wordpress-plugin/airano-mcp-bridge. - Eight new endpoints: /capabilities, /bulk-meta, /export, /cache-purge, /transient-flush, /site-health, /audit-hook, /upload-and-attach. - wp.org Plugin Check pass: i18n, WP_Filesystem, scheme allowlist on audit-hook URL. Other - Gitea ergonomics (F.17): batch files, tree, search, compare, releases, fork. - Opportunistic bcrypt upgrade for legacy SHA-256 admin keys (F.8). - n8n refactor: structured errors, capability probe, missing tools backfilled. - Idempotency-Key dedup for AI media upload retries; WP client fast-fails on unreachable sites. Docs - README + CLAUDE.md drop the fixed "633 tools" claim. The total grows with each release; per-plugin approximations + dashboard-surfaced counts replace it. - Tools/Tests badges removed in favour of "Plugins: 10". Deployment - PyPI mirror chain, optional BUILD_HTTP_PROXY, Alpine→Yandex apk mirror, Debian-slim Plan-B Dockerfile, mirror.gcr.io variant. CI - Black + Ruff clean on Python 3.12; pytest tests/ green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Testing Guide
Integration Tests
Quick Start
# In Docker container:
docker exec -it mcphub python tests/run_integration_tests.py
# Or local:
python tests/run_integration_tests.py
What Gets Tested
- Module Imports - All modules load correctly
- BasePlugin Architecture - Plugin system compatibility
- WordPress Plugin - Initialization and handlers
- Tool Specifications - Format and completeness
- Handlers Structure - All 14 handlers present
- Pydantic Schemas - Validation working
- ToolGenerator Integration - Dynamic tool generation ready
Expected Output
Running Integration Tests for WordPress MCP Server
============================================================
Running: Imports... PASSED
Running: Base Plugin... PASSED
Running: WordPress Plugin Init... PASSED
Running: Tool Specifications... PASSED
Running: Handlers Structure... PASSED
Running: Pydantic Schemas... PASSED
Running: ToolGenerator Integration... PASSED
============================================================
Test Summary:
Total: 7
Passed: 7
Failed: 0
Skipped: 0
Exit Codes
0- All tests passed1- Some tests failed
JSON Output
The script also outputs results as JSON for programmatic parsing:
{
"timestamp": "2025-11-16T10:30:00",
"tests": [
{
"name": "imports",
"status": "passed",
"message": "All modules imported successfully",
"details": {}
}
],
"summary": {
"total": 7,
"passed": 7,
"failed": 0,
"skipped": 0
}
}
Manual Testing with Real Sites
To test with real sites, use MCP Inspector or Claude Desktop:
# Test health
wordpress_get_site_health(site="mysite")
# Test posts
wordpress_list_posts(site="mysite", per_page=5)
# Test products
wordpress_list_products(site="mysite", per_page=5)
# Test WP-CLI (requires container access)
wordpress_wp_cache_type(site="mysite")
Troubleshooting
Import Errors
Error: ModuleNotFoundError: No module named 'plugins'
Fix: Run from project root:
cd /app # In Docker
python tests/run_integration_tests.py
Handler Errors
Error: Can't instantiate abstract class WordPressPlugin
Fix: This means BasePlugin still has abstract get_tools(). This should be fixed in the latest version.