WP-CLI AI Command with MCP support

Created By
mcp-wpa year ago
Control WordPress using WP-CLI, AI, and MCP.
Overview

What is AI Command?

AI Command is a tool that allows users to control WordPress using WP-CLI, AI, and MCP (Multi-Channel Protocol). It integrates AI services with WordPress to enhance functionality and automation.

How to use AI Command?

To use AI Command, ensure you have WP-CLI v2.11 or greater installed. You can install the package using the command: wp package install mcp-wp/ai-command:dev-main. Make sure to have the AI Services plugin installed on your WordPress site.

Key features of AI Command?

  • Control WordPress through command line interface (CLI) using AI.
  • Integration with AI Services plugin for enhanced capabilities.
  • Easy installation and setup process.

Use cases of AI Command?

  1. Automating WordPress tasks using AI commands.
  2. Managing WordPress sites more efficiently through CLI.
  3. Enhancing WordPress functionality with AI-driven features.

FAQ from AI Command?

  • What is required to install AI Command?

You need WP-CLI v2.11 or greater and the AI Services plugin installed on your WordPress site.

  • Can I report bugs or request features?

Yes! You can report bugs or request features by creating an issue on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mcp-wp
Star
71
Language
PHP
License
Apache-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago