JetEngine MCP Server: Complete Setup and Integration Guide
Crocoblock’s JetEngine 3.8.0 (released November 2025) introduced a Model Context Protocol server that enables AI assistants like Claude to directly interact with WordPress sites—creating custom post types, meta boxes, taxonomies, and queries through natural language commands. The MCP Server acts as a secure middleware layer, exposing a controlled set of JetEngine capabilities without granting AI systems direct database or admin access.
How the JetEngine MCP Server works
The MCP Server is not a physical server but software running on your WordPress hosting that exposes a REST API endpoint at wp-json/jet-engine/v1/mcp/. When an AI client connects, it receives context about your site’s configuration (post types, taxonomies, meta boxes, installed plugins) and can execute a predefined set of safe operations.
The architecture follows the Model Context Protocol specification—an open standard for AI-to-application communication. JetEngine’s implementation provides two categories of operations: Tools (write operations that modify your site) and Resources (read-only operations that provide context). This separation ensures AI systems can understand your site structure before attempting modifications.
Crocoblock designed this with security constraints: AI cannot access the database directly, cannot modify core WordPress settings, and is limited to JetEngine-specific operations. The authentication layer uses WordPress’s native Application Passwords system, requiring valid credentials for every request.
Authentication with WordPress Application Passwords
JetEngine MCP uses Basic HTTP authentication with WordPress Application Passwords—a built-in WordPress feature for API access without exposing your main password.
To create an Application Password:
- Navigate to WordPress Dashboard → Users → Profile
- Scroll to the Application Passwords section
- Enter a descriptive name (e.g., “Claude Desktop MCP”)
- Click Add Application Password
- Copy the generated password immediately—it displays only once
The authentication token is constructed by Base64-encoding your credentials in the format username:applicationpassword. For example, if your username is admin and your application password is XXXX XXXX XXXX XXXX XXXX XXXX, you would encode admin:XXXX XXXX XXXX XXXX XXXX XXXX to produce your authorization token.
Claude Desktop configuration format
Since JetEngine exposes a remote HTTP endpoint (not a local stdio server), Claude Desktop requires the mcp-remote npm package to bridge the connection. This package handles the HTTP-to-stdio translation that Claude Desktop expects.
Prerequisites: Node.js v16+ must be installed on your system.
The configuration file location varies by operating system:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Here is the exact JSON configuration:
{
"mcpServers": {
"jetengine": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://your-website.com/wp-json/jet-engine/v1/mcp/",
"--header",
"Authorization:Basic YOUR_BASE64_TOKEN_HERE"
]
}
}
}
Critical note: There is no space between Authorization:Basic and the token in the header argument due to a bug in Claude Desktop on Windows where spaces in arguments are not properly escaped. Using the format shown above works reliably across platforms.
An alternative configuration using environment variables for cleaner credential management:
{
"mcpServers": {
"jetengine": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://your-website.com/wp-json/jet-engine/v1/mcp/",
"--header",
"Authorization:Basic ${WP_AUTH_TOKEN}"
],
"env": {
"WP_AUTH_TOKEN": "YOUR_BASE64_ENCODED_CREDENTIALS"
}
}
}
}
After saving the configuration, restart Claude Desktop completely. A hammer/tools icon should appear in the chat input area when the connection succeeds.
Available tools and CRUD capabilities
The MCP Server exposes 11 distinct operations across content creation and configuration retrieval.
Write operations (Tools)
| Tool | Capability |
|---|---|
| Add Custom Post Type | Creates CPTs with associated meta fields, labels, and WordPress registration parameters |
| Add Custom Content Type | Creates CCTs using JetEngine’s independent database storage |
| Add Taxonomy | Registers custom taxonomies and assigns them to post types |
| Add Meta Box | Creates field groups assignable to posts, taxonomies, users, or WooCommerce products |
| Add Glossary | Generates reusable option lists for Select/Radio/Checkbox fields |
| Add Query Builder Query | Creates posts, terms, users, CCT, SQL, or comments queries |
| Add Listing Grid Item | Generates listing template structures based on existing queries |
| Manage JetEngine Modules | Lists, activates, or deactivates JetEngine modules |
Read operations (Resources)
| Resource | Returns |
|---|---|
| Get JetEngine Configuration | Complete setup details including all CPTs, CCTs, meta boxes, taxonomies, relations, and queries |
| Get Website Configuration | Registered post types, taxonomies, and installed plugins in JSON format |
| Get JetEngine Macros | Available dynamic macros with arguments and usage examples |
Key limitations to understand
The MCP Server cannot create taxonomy terms—only taxonomy types. Listing templates generate without styling (structure only). Meta fields cannot be added directly to CPTs through the MCP interface; you must use the Meta Box tool and assign it to the CPT. Complex operations like queries may produce variable results due to the many possible parameter combinations.
Enabling the MCP Server in WordPress
The server requires explicit activation:
- Go to WordPress Dashboard → JetEngine → JetEngine
- Select the MCP Server tab
- Enable the “Enable MCP Server” toggle
- The page displays your MCP Server URL and lists available tools
JetEngine 3.8.0 or higher is required. The feature was released as Beta in November 2025.
Official Crocoblock documentation resources
Crocoblock provides several official guides for the MCP Server implementation:
- Primary setup guide:
crocoblock.com/blog/jetengine-ai-command-center-mcp-guide/— comprehensive walkthrough of MCP Server and Command Center with practical examples - VS Code/Copilot integration:
crocoblock.com/knowledge-base/jetengine/how-to-use-mcp-server-with-vs-code-copilot/— technical configuration guide applicable to any MCP client - Dashboard settings reference:
crocoblock.com/knowledge-base/features/jetengine-dashboard-settings-overview/— documents the MCP Server settings panel - Elementor Angie integration:
crocoblock.com/blog/wordpress-elementor-ai-angie-with-jetengine/— explains JetEngine’s integration with Elementor’s AI agent
The VS Code documentation is particularly useful for Claude Desktop setup as it covers the same authentication and endpoint configuration concepts.
Companion feature: Command Center
JetEngine 3.8.0 also introduced Command Center—a built-in AI chat interface at Crocoblock → Command Center in WordPress. Unlike external MCP connections, Command Center requires an OpenAI API key and uses your API balance. It provides the same MCP tools through a native WordPress interface, useful for users who prefer working directly in the admin dashboard rather than through external AI clients.
Conclusion
The JetEngine MCP Server represents a significant advancement in AI-WordPress integration, offering a standardized, secure interface for AI assistants to create and manage JetEngine components. The implementation uses familiar WordPress authentication patterns and follows the open Model Context Protocol specification, making it compatible with Claude Desktop, VS Code Copilot, ChatGPT, and other MCP clients. The key practical consideration is using mcp-remote as a bridge for Claude Desktop and ensuring the Base64-encoded credentials are correctly formatted in the authorization header.
