Agent API & MCP

LumaWP is built to be operated by agents as well as people. A scoped agent key lets an AI agent read plans, launch a WordPress site for its owner, watch provisioning and return the result — without sharing a password or using browser automation.

Human first, agent second. The owner creates the key in the panel and keeps ownership, billing and revocation. Agent actions appear in the same panel as actions taken by a person.

Create a key

  1. Sign in at app.lumawp.com and select the organisation that should own the sites.
  2. Open Settings → AI & API and create a key. It is shown once; store it in your agent's secret manager.
  3. Give the key only to the agent you intend to operate. Revoke it at any time.

Authentication

Send the key as a bearer token. Keys are scoped to one Clerk organisation and can only touch that organisation's sites.

Authorization: Bearer wpl_agent_…

REST Agent API

Base URL: https://app.lumawp.com/api/v1

MethodPathPurpose
GET/api/v1/plansRead the live plan catalogue.
GET/api/v1/sitesList sites owned by the key's organisation.
POST/api/v1/sitesProvision a site: { slug, plan?, php_version? }.
GET/api/v1/sites/{slug}Read status, hostname, plan and links.
DELETE/api/v1/sites/{slug}Delete the site after explicit confirmation.

Launch a site

curl -X POST https://app.lumawp.com/api/v1/sites \
  -H "Authorization: Bearer $LUMAWP_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"slug":"acme-studio","plan":"pro"}'

The response is 202 Accepted with the site id, hostname and provisioning status. Poll GET /api/v1/sites/acme-studio until status is active; the response includes the public URL and the panel link.

MCP server

Connect a Model Context Protocol client to https://app.lumawp.com/api/mcp with the same bearer key:

{
  "mcpServers": {
    "lumawp": {
      "type": "http",
      "url": "https://app.lumawp.com/api/mcp",
      "headers": { "Authorization": "Bearer ${LUMAWP_AGENT_KEY}" }
    }
  }
}

Available tools:

Safety & limits

Back to LumaWP