home / mcp / optimizely dxp mcp server
Provides a REST API and stdio workflow to manage deployments, logs, storage, and real-time monitoring for Optimizely DXP with automation-ready tooling.
Configuration
View docs{
"mcpServers": {
"jaxondigital-optimizely-dxp-mcp": {
"url": "https://mcp.example.com/mcp",
"headers": {
"REDIS_HOST": "localhost",
"REDIS_PORT": "6379",
"DXP_MCP_HOST": "0.0.0.0",
"DXP_MCP_MODE": "http",
"DXP_MCP_PORT": "3001",
"REDIS_ENABLED": "false",
"REDIS_PASSWORD": "your-redis-password",
"OPTIMIZELY_PROJECT_ID": "your-project-id",
"OPTIMIZELY_PROJECT_KEY": "your-key",
"OPTIMIZELY_PROJECT_SECRET": "your-secret"
}
}
}
}You transform Optimizely DXP into an AI-powered, autonomous operations platform. The MCP Server lets you manage deployments, logs, databases, storage, and real-time monitoring through a REST API or a zero-setup stdio workflow. It enables scalable automation, real-time event subscriptions, and error-resilient operations so you ship faster and with less manual toil.
You interact with the MCP Server through an MCP client or automation platform. There are two transport modes, and you can choose the one that fits your workflow: a direct HTTP REST API mode for remote automation, or a stdio mode for local AI clients and Claude Desktop. In either mode, you access 45 tools that cover permission checks, deployments, logs, databases, storage, multi-project management, configuration utilities, and advanced features. Use these tools to perform operations, subscribe to real-time deployment events, and retrieve structured data for your automation pipelines.
Prerequisites: you need Node.js 18+ (LTS recommended) and an Optimizely DXP project with API credentials.
{
"mcpServers": {
"optimizely-dxp": {
"command": "npx",
"args": ["-y", "@jaxon-digital/optimizely-dxp-mcp"],
"env": {
"OPTIMIZELY_PROJECT_ID": "your-project-id",
"OPTIMIZELY_PROJECT_KEY": "your-key",
"OPTIMIZELY_PROJECT_SECRET": "your-secret"
}
}
}
}For HTTP-based automation platforms, you can run the MCP as an HTTP server with a JSON-RPC 2.0 API. The server exposes the /mcp endpoint for tool calls and /health for readiness checks. If you run via Docker, pass the required environment variables for your Optimizely project and enable HTTP transport.
If you prefer stdio (local development or Claude Desktop), you start the MCP by configuring a stdio-based MCP server in your client configuration. Claude will start and stop the MCP as needed, without manual intervention.
The MCP supports multiple environment variables to tailor deployment contexts, transport mode, and Redis caching. Common variables include project credentials and transport settings. Ensure you provide the correct IDs, keys, and secrets for your Optimizely DXP project.
If you enable HTTP mode, set the transport mode and port, for example DXP_MCP_MODE=http and DXP_MCP_PORT=3001. For Redis caching, you can enable Redis with REDIS_HOST, REDIS_PORT, REDIS_PASSWORD, and REDIS_ENABLED.
Do not run the MCP server as a traditional background process. The MCP is started and stopped automatically by the client (Claude or your automation platform) and is designed to run on demand. If you encounter issues, verify credentials, ensure the DXP API access is enabled, and test the connection with the test tool.
Validate setup and show capabilities
Detailed environment access breakdown
Confirm specific environment access
System status with structured health data
Show deployment history with filters
Initiate code deployment
Real-time progress with auto-refresh
Finish verification state
Rollback if needed
Current status with wait-then-check support
Sync content between environments
Show content copy history
Interactive export workflow with smart monitoring
Progress tracking with auto-download flag
Get export file with background progress
Export history and monitoring
Stream and analyze in-memory for faster log analysis
Side-by-side log comparison for deployment decisions
Download with manifest tracking
Show available log containers
Find logs by date range and type
Progress tracking for active downloads
Show blob containers with structured data
Incremental blob downloads with parallelism
Create temporary blob access URLs
Show completed downloads with manifests
Show all configured projects
Change active project context
Display active project info
Context-aware best practices
Version info with update checks
Show download configuration
Configure download paths by type
Progress for all background downloads
Stop background download
Show API quota and limits
Redis cache statistics (if enabled)
Track DXP CMS version updates
Configure HTTP log streaming
Disable HTTP log streaming
Show tool availability in current context
NEW: MCP Resources for real-time updates