mix.core

Mixcore CMS is an open-source enterprise web application platform. The MCP server provided here is primarily intended to enable running the Mixcore CMS Docker image in a containerized environment, exposing the CMS front-end/UI and back-end services via a local port. Once the container is running, you can access the admin portal through the mapped port (default 5000 on the host as configured above) and interact with the APIs and dashboards that come with Mixcore. Use the included Docker image to experience the full stack: the back-office built on ASP.NET Core with a modular architecture, a front-end portal, and integrated services for content management, multilingual support, and extensibility. The tooling enables you to manage databases, authentication/identity, and module assets through the CMS UI and API.

Prerequisites:

• Docker installed and running on your machine.
• Internet access to pull the Mixcore CMS Docker image.

Install steps:

1. Pull the latest Mixcore CMS image: docker pull ghcr.io/mixcore/mix.core:master

2. Run the container and expose the CMS on port 5000 (adjust as needed): docker run -it --rm -p 5000:80 --name mixcore_cms ghcr.io/mixcore/mix.core:master

3. Open your browser and navigate to http://localhost:5000 to access the admin portal and frontend.

Optional (Docker Compose):

1. Create a docker-compose.yml with the following minimal setup: version: '3' services: mixcore: image: ghcr.io/mixcore/mix.core:master ports: - "5000:80" restart: unless-stopped

2. Start the stack: docker-compose up -d

3. If you prefer running from source with .NET SDK, refer to the official Mixcore docs for building and running the CMS locally using dotnet (not required for MCP usage here).

Tips and common issues:

• Ensure Docker has enough memory and CPU assigned; the CMS runs a combination of ASP.NET Core services and front-end tooling.
• If you encounter port conflicts, change the host port mapping (the 5000:80 mapping in the example).
• The Mixcore image exposes an API and admin portal; you can configure environment variables (MIXCORE_ENV, MIXCORE_API_URL) as needed for your deployment.
• If you plan to modify or extend modules, refer to the repository’s modular architecture and the optional NuGet-based libraries as outlined in the project docs.
• For production deployments, consider using a reverse proxy (e.g., Nginx) and configuring SSL certificates for the exposed domain.