Get the FREE Ultimate OpenClaw Setup Guide →

wordpress-agentic-ui-generator

Convert any Wordpress website into an MCP app

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio mnfst-wordpress-agentic-ui-generator npm run dev

How to use

This MCP server is a WordPress-focused Agentic UI generator built as a monorepo with a frontend, backend, and shared types. When running the provided development script, both the frontend (React + Vite) and the backend (NestJS) start concurrently, enabling you to generate and manage MCP servers that render an agentic UI for WordPress content. Use the backend API to create, list, and sync MCP servers and access the MCP endpoints to send and receive messages. The frontend provides a UI to configure and view generated MCPs, while the backend handles the server lifecycle, storage, and synchronization with WordPress data sources.

How to install

Prerequisites:

  • Node.js 18.0.0 or newer
  • Docker (for MySQL database)
  1. Install dependencies and start services
# Install root dependencies
npm install

# Start development (this runs frontend + backend in parallel)
npm run dev
  1. Start the MySQL container (Docker)
npm run docker:up

This spins up a MySQL 8.0 container with:

  • Database: mcp_generator
  • User: mcp_user
  • Password: mcp_password
  • Port: 3306

3) Configure environment for the backend
```bash
cp packages/backend/.env.example packages/backend/.env

The default values work with the Docker-based database setup.

  1. (Optional) Build for production
# Build all packages
npm run build

# Build specific package
npm run build:frontend
npm run build:backend
  1. Start production backend (after building)
npm run start:backend

Notes:

  • The frontend proxies API requests to the backend automatically during development.
  • Ensure Docker is running if you rely on the MySQL container.

Additional notes

Tips and considerations:

  • If you change database credentials in the backend .env file, ensure they match the Docker container settings.
  • The dev script starts both frontend and backend; use dev:frontend or dev:backend to run individually.
  • When deploying, you may want to run only the backend API and deploy the frontend separately to a static host or CDN.
  • Monitor API endpoints like GET /api/mcp-servers and POST /api/mcp-servers for MCP server management.
  • If you encounter port conflicts, stop other services using ports 3000 (backend) or 5173 (frontend).

Related MCP Servers

Sponsor this space

Reach thousands of developers