Smithery/Cloud-WP Control Nexus (Tanuki Edition)

An enterprise-grade MCP server framework tailored for deep WordPress lifecycle automation. This nexus facilitates the creation, maintenance, and customization of WordPress installations utilizing the Model Context Protocol (MCP), ensuring compatibility across AI environments like Cursor, Claude, and other MCP-compliant interfaces.

What is the WP Control Nexus?

This is a managed automation layer designed to execute intricate WordPress operations via a dedicated web portal. It harnesses the power of MCP integration alongside direct, secure calls to the native WordPress REST API, delivering an unparalleled, unified automation experience.

Core Advantages: - Abstraction layer requiring zero legacy scripting knowledge - Encrypted, secure linkage to target WordPress installations - Robust, predefined automation sequences - Instantaneous visual feedback on configuration changes - Unified management across disparate site instances - Highly ergonomic, streamlined graphical control surface

Nexus Plugin Integration for WP Admin

The Nexus Dashboard Connector plugin embeds the core capabilities of the Control Nexus directly inside your WordPress administrative backend. Setup instructions:

Initialization Steps

1. Deploy and enable the Nexus Dashboard Connector plugin on the target WordPress instance.
2. Navigate to the Nexus configuration panel within the WP admin area.
3. Input the required connection parameters:
4. Service Endpoint: Set to https://wordpress-mcp.onrender.com/api/v1/
5. Security Credential: Input the primary access token 3c9a406341969edf38b3d6d0c8f7685c

Exposed REST Interface

The primary Nexus server exposes the following interaction points for the dashboard module:

• POST /api/v1/edit-site - Transmits instructions for site content editing
• POST /api/v1/execute-workflow - Initiates complex, multi-step operational routines

Request Security

All outbound traffic originating from the dashboard plugin mandates these HTTP headers: - Authorization: Bearer 3c9a406341969edf38b3d6d0c8f7685c - Content-Type: application/json

Output Schema

All endpoint responses adhere strictly to one of these JSON structures: - Success: { "status": true, "payload": {...} } - Failure: { "status": false, "detail": "Descriptive failure narrative" }

Comprehensive Feature Set

• Core WordPress environment configuration utilities
• Conceptualization and blueprinting tools
• Rapid prototyping and design specification generation
• Structural mapping and visualization of site architecture
• Content generation and lifecycle management
• Active theme modification and asset control
• Digital asset library administration
• Navigation structure (Menus/Widgets) governance
• User provisioning and permission control
• Seamless integration with WooCommerce electronic commerce modules
• Search Engine Optimization (SEO) enhancement utilities
• Visual presentation audit capabilities
• Path-to-conversion mapping and flow refinement
• Data capture mechanism design and analysis
• Systematic content review and platform refinement

Onboarding Guide

Integration with Cursor IDE

To link the WP Control Nexus with the Cursor development environment:

1. Verify Cursor installation readiness (obtain binary from [cursor.sh])
2. Establish or modify the configuration file at ~/.cursor/mcp.json (global scope) or .cursor/mcp.json (project scope) to include:

{ "mcpServers": { "tanuki-wordpress": { "command": "cmd", "args": [ "/c", "npx", "-y", "@smithery/cli@latest", "run", "remote", "--url", "https://wordpress-mcp.onrender.com/sse-cursor", "--key", "YOUR_API_KEY_HERE" ] } } }

1. Relaunch the Cursor application.
2. Engage the Cursor chat interface and request utilization of the WordPress toolset.

Utilizing via Smithery CLI

The WP Control Nexus is published on the Smithery registry. Direct invocation is possible via:

npx @smithery/cli run @tanuki/wordpress-mcp

Self-Contained Deployment

Deploy this MCP service instance onto your proprietary infrastructure:

1. Fork the source repository.
2. Execute npm install.
3. Define all mandatory environment configuration parameters (details below).
4. Initiate the service with npm start.

Phase 1: Site Prerequisite Check

Prior to establishing communication with WordPress:

Phase 2: WordPress Site Preparation

Ensure the following prerequisites are met before linking your WordPress installation to the Nexus:

1. A live, accessible WordPress instance is operational, with full administrative credentials available.
2. Creation of an Application Password:
3. Access the WordPress administrator panel.
4. Navigate to Users → Profile settings.
5. Locate the "Application Passwords" section.
6. Assign a descriptive label (e.g., "NexusController").
7. Initiate the password generation process.
8. Securely record the resulting password for subsequent configuration steps.

Phase 3: Nexus Connection Establishment

To finalize the linkage between your site and the WP Control Nexus:

1. Log into the main TanukiMCP operator dashboard.
2. Select the "Integrate New WordPress Instance" option.
3. Input the full site URL.
4. Supply the WordPress administrative username and the Application Password generated previously.
5. Click "Authorize Connection".

Upon successful authorization, the instance will appear in your dashboard, unlocking workflow creation and tool utilization capabilities.

Available Operational Tools

Design & Planning Layer

• Strategy Architect: Formulate comprehensive organizational strategies for WP deployments.
• Layout Modeler: Construct detailed schematic blueprints for site page structure.
• Ideation Engine: Generate novel concepts and reference materials for WP design.
• Specification Generator: Produce exhaustive design documentation for project artifacts.
• Design Token Manager: Standardize and govern visual style variables for brand consistency.
• Structural Map Utility: Visualize and output the complete information architecture (IA).
• Theme Comparator: Evaluate and select optimal themes against specified criteria.
• Change Log Planner: Document modifications with structured before-and-after reports.
• Sitemap Composer: Generate and manage site navigation maps.

Execution & Implementation Layer

• Instance Auditor: Retrieve comprehensive metadata regarding the connected WP installation.
• Content Repository Handler: Manipulate core WP entities (pages, articles, custom types).
• Identity Manager: Administer system users and their associated roles/permissions.
• Plugin Orchestrator: Control plugin lifecycle (install, enable, configure).
• System Regulator: Modify overarching WordPress application configurations.
• Site Fabricator: Toolset for building complete, functional WordPress websites from scratch.
• Core Configuration Tool: Adjust fundamental WP options and site-wide parameters.
• Modification Enforcer: Systematically apply changes documented in the planning phase.
• Visual Style Customizer: Directly adjust theme aesthetics.
• Theme Lifecycle Manager: Manage theme assets and installations.
• Navigation Fabricator: Configure navigational menus.
• Interface Element Manager: Control sidebar and footer widgets.
• Asset Ingestor: Manage the media library.
• E-commerce Engine: Configure and oversee WooCommerce store functionality.

Review & Refinement Layer

• Aesthetic Reviewer: Critique visual design elements and propose enhancements.
• Data Integrity Checker: Audit existing content for quality assurance and coherence.
• Platform Finisher: Apply final polish and minor systemic improvements.
• Search Visibility Optimizer: Implement best practices for search engine indexing.
• User Flow Surveyor: Model and optimize paths users take through the digital experience.
• Path Optimizer: Analyze and refine site navigation logic.
• Interaction Designer: Build and evaluate form systems.

Platform Utilization Methods

The Tanuki Control Nexus offers three primary modalities for automating your WordPress environment:

1. Curated Operational Blueprints

Select from and execute our library of pre-validated operational workflows:

• Redesign of the primary landing page
• E-commerce backend initialization
• Content freshness update cycle
• Search engine visibility boost routine
• Media repository archival/cleanup
• Plus numerous other automated sequences

2. Adaptive Workflow Construction

Assemble bespoke, multi-step automation sequences:

1. Designate the target WordPress environment.
2. Select requisite tools from our expansive catalog.
3. Define precise input parameters for every operational stage.
4. Persist the sequence for recurrent execution.
5. Initiate the blueprint execution and observe progress feedback in real-time.

3. Granular Tool Invocation

Invoke individual utilities for specific, isolated tasks:

1. Identify and select the required utility.
2. Specify the necessary operational arguments.
3. Execute the utility and immediately review the resultant state change.

Real-Time Visualization Feature

Our signature Live Preview capability offers immediate visual confirmation of automated alterations:

• Observe the AI agent applying modifications to the live site environment instantaneously.
• Option to sanction, alter, or veto proposed changes.
• Toggle between rendering modes (e.g., visual editor, raw source, mobile viewport).
• Compare the configuration state before and after the operation.
• Guarantee comprehensive oversight throughout the automation process.

Diagnostics and Fault Resolution

Should operational issues arise while utilizing the WP Control Nexus:

1. Connectivity Failures: Reconfirm site accessibility and validate the accuracy of the Application Password.
2. Blueprint Malfunctions: Scrutinize the execution logs for specific error codes or messages.
3. Tool Dependency: Certain specialized tools might necessitate prerequisite WordPress plugins or custom configurations.
4. Browser Interface Issues: Ensure the client is using a modern, up-to-date web browser (Chrome, Firefox, Safari, Edge).
5. Interface Stale State: Attempt clearing the local browser cache if UI elements appear corrupted.

Environmental Configuration Variables

The WP Control Nexus server requires/accepts the following settings via environment variables:

Mandatory Setup Parameters

TANUKIMCP_MASTER_KEY=your_master_api_key

Optional Service Tuning

PORT=3001 (Default operation port) REQUIRE_API_KEY=true (Recommended security posture) HEADLESS=true (For server-side automation without GUI interaction) CORS_ALLOW_ORIGIN=* (Permits cross-origin resource sharing from all domains) CORS_ALLOW_METHODS=GET,HEAD,PUT,PATCH,POST,DELETE,OPTIONS CORS_ALLOW_HEADERS=Content-Type,Authorization,Accept,Origin,X-Requested-With,X-Api-Key

Generative Model Configuration (OpenAI Backend)

OPENAI_API_KEY=your_openai_api_key OPENAI_MODEL=gpt-4.1 OPENAI_ADVANCED_MODEL=gpt-4.1 OPENAI_BASIC_MODEL=gpt-4.1-mini OPENAI_NANO_MODEL=gpt-4.1-nano OPENAI_MAX_TOKENS=4096 OPENAI_TEMPERATURE=0.7 OPENAI_MAX_CONTEXT_TOKENS=128000

Telemetry Configuration

ANALYTICS_SAVE_INTERVAL_MS=300000 ANALYTICS_DETAILED_LOGGING=false

Critical Note: WordPress access particulars (site address, credentials, app password) are transmitted on a per-call basis within the request payload by the Nexus Dashboard module and must NEVER be hardcoded as persistent environment variables in a live deployment. The server expects this sensitive data in the body of each API transaction.

Security Protocol

The WP Control Nexus implements a streamlined security framework:

1. Primary Authorization Token: All interaction requests must carry the master key within the Authorization header:

Authorization: Bearer 3c9a406341969edf38b3d6d0c8f7685c

1. Consumer Identification: Each request must explicitly identify the interacting WordPress user via the request body:

{ "context_user_id": 123, "command": "Your instruction payload" }

This methodology simplifies authorization while facilitating precise usage attribution per WordPress user session.

OpenAI Model Interoperability

The WP Control Nexus natively interfaces with OpenAI's GPT-4.1 family of models to power intelligent site management operations. The architecture supports tiered model selection:

• GPT-4.1 (Premium): Utilized for the most complex, analytical, or code-intensive WordPress remediation tasks.
• GPT-4.1 Mini (Standard): A balanced option offering speed and cost efficiency for common operations.
• GPT-4.1 Nano (Utility): The most rapid and economical tier, suitable for simple data retrieval or basic content formatting.

The API layer enables intelligent resource allocation through:

1. Deep integration of WordPress functional knowledge (themes, core, plugins).
2. Autonomous site modification capabilities.
3. Automated execution routing for repetitive WordPress chores.
4. Integrated token consumption monitoring and reporting.

Users dictate the required computational complexity via the model_preference parameter in their input: - premium: Activates the full GPT-4.1 model. - standard: Activates the GPT-4.1-mini model.

Interface Routes

Dashboard Connector Endpoints

• POST /api/v1/edit-site - Delivers visual editing commands to the site

{ "instruction": "User message content", "site_endpoint": "https://example.com", "site_auth_token": "xxxx xxxx xxxx xxxx", "context_user_id": 123, "model_preference": "premium" }

• POST /api/v1/execute-workflow - Triggers a predefined process chain

{ "blueprint": "image_optimization_run", "arguments": { "compression_level": 85, "scale_assets": true }, "context_user_id": 123 }

Monitoring and Reporting Routes

• GET /api/v1/analytics/token-usage?context_user_id=123&verbose=true - Retrieve detailed token utilization data
• GET /api/v1/analytics/monthly-report?period=2023-01 - Access summarized monthly consumption reports

Operational Assistance

If you require support for the Tanuki Control Nexus:

• Codebase Queries: Submit an official issue ticket on the corresponding GitHub project.
• Direct Contact: Reach out to the support team at support@tanukimcp.com.

Commercial Structure

The Tanuki Control Nexus offers scalable commercial agreements to match varying operational scales. Current plans are detailed at [tanukimcp.com/pricing]:

• Individual Tier: Optimized for single-site management.
• Agency Tier: Designed for consulting firms overseeing diverse client installations.
• Corporate Tier: Bespoke arrangements for large-scale infrastructure management.

All subscriptions grant access to the fundamental automation toolkit; higher tiers unlock augmented workflow capacity, increased site quotas, and access to advanced utilities.