SJS.Neos.MCP

SJS.Neos.MCP provides a dedicated MCP (Model Context Protocol) server for Neos CMS 9.x. It exposes a set of feature-driven tools that integrate with Neos to allow model-context aware operations, tooling, and inspection via the MCP protocol. The server is configured to load feature sets such as Neos integration, content repository access, and resource management, enabling developers to interact with Neos content and behavior through MCP clients and the MCP Inspector UI. By registering multiple feature sets under server.mcp.featureSets, you can extend or customize the capabilities exposed by the MCP server for your Neos installation. The project emphasizes that this is a development road for MCP support on Neos 9 and may change, so expect updates to tooling and configuration in future releases. When running, you can pair the MCP server with the MCP Inspector to test tool behaviors, preview actions, and verify downstream effects in a controlled UI environment.

Prerequisites:

• System with Docker installed
• Basic familiarity with Neos CMS 9.x and Composer

Installation steps:

1. Prepare Neos project and dependencies:

   • Ensure Neos 9.x is installed and your project is configured to use the MCP feature sets.
   • Install feature sets (examples shown in Quick Start): composer require sjs/neos-mcp-feature-set-neos composer require sjs/neos-mcp-feature-set-cr composer require sjs/neos-mcp-feature-set-resources
   • Optionally install test feature set for development: composer require sjs/neos-mcp-feature-set-test

2. Run the MCP server (Docker):

   • Ensure the docker image is available or pull from registry: docker pull sjsneos/mcp-server:latest
   • Start the server container (adjust according to your environment): docker run -i --env NEOS_VERSION=9.x --env MCP_CONFIG_PATH=Configuration/Settings.Server.yaml --env LOG_LEVEL=info --env ENVIRONMENT=production sjsneos/mcp-server:latest

3. Verify and connect:

   • Ensure your MCP Inspector or client is configured to connect to the server endpoint exposed by the container.
   • Validate that the feature sets are registered under server.mcp.featureSets in Configuration/Settings.Server.yaml and that the MCP server responds with the expected tools.

Tips and common issues:

• If your Neos project uses a different configuration path, update MCP_CONFIG_PATH in the environment variables accordingly.
• The server is marked as under development for Neos 9; keep an eye on Roadmap.md and update notes for breaking changes.
• When extending with new FeatureSets, follow the naming convention where prefixes derive from the class name (e.g., WorkspaceFeatureSet -> workspace_prefix) and register the class under server.mcp.featureSets in Configuration/Settings.Server.yaml.
• Check that Docker networking allows the MCP container to reach any Neos services it needs (e.g., Content Repository or Resource services) if those are exposed separately.
• Enable verbose logging (LOG_LEVEL=debug) while debugging feature registration or tool invocation.