WP Engine MCP Server

Created By
jpollocka year ago
Sample MCP server for WP Engine API
Overview

What is WP Engine MCP Server?

WP Engine MCP Server is a TypeScript implementation of a server designed to interact with the WP Engine API, providing tools for managing WP Engine accounts, sites, installs, and backups.

How to use WP Engine MCP Server?

To use the server, clone the repository, install dependencies, and configure your WP Engine API credentials. You can run the server locally or remotely using HTTP transport.

Key features of WP Engine MCP Server?

  • Retrieve account, site, and install information.
  • Create and manage backups.
  • Support for both local (stdio) and remote (HTTP) connections.
  • Comprehensive logging and error handling.

Use cases of WP Engine MCP Server?

  1. Managing multiple WP Engine accounts and sites.
  2. Automating backup processes for WordPress installations.
  3. Integrating with other tools for enhanced WP Engine management.

FAQ from WP Engine MCP Server?

  • How do I authenticate with the WP Engine API?

You need to set the WP_ENGINE_API_USERNAME and WP_ENGINE_API_PASSWORD environment variables with your API credentials.

  • Can I run the server locally?

Yes! You can run the server using local MCP clients with stdio transport.

  • What transport options are available?

The server supports both stdio and HTTP transport options.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jpollock
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
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.

21 hours ago