Apache Sling MCP Server

Experimental MCP Server implementation for Apache Sling.

Development

Build the project with Maven and start up the MCP server, based on the Apache Sling Starter:

$ mvn install feature-launcher:start feature-launcher:stop -Dfeature-launcher.waitForInput

Then build and deploy the MCP server contributions bundle from the Sling Whiteboard:

$ mvn -f whiteboard/mcp-server-contributions/ install sling:install 

Then open up your coding assistant tool and add an remote MCP server with location http://localhost:8080/mcp . Access is only permitted for the admin user therefore basic authentication headers need to be specified. In case of the default credentials the configuration can look as follows

"aem-cs-sdk": {
  "type": "streamable-http",
  "url": "http://localhost:8080/bin/mcp",
  "headers": {
    "Authorization": "Basic YWRtaW46YWRtaW4="
  }
}

Please refer to the documentation of your coding assistant tool for details on how to add a remote MCP server and specify authentication headers.

Deployment

The src/main/features/main.json files contains bundles and configurations that are required for deploying on top of the version of the Sling Starter defined in pom.xml.

This file is intended mostly for local development but can also be used as a blueprint for including the bundle in Sling Starter based deployments.

To obtain a ready to use target file:

• build the project with mvn package
• copy the file target/slingfeature-tmp/main.json to your own project
• adjust the metadata from the feature file as needed ( id, title, etc )

Legacy artifact

For applications still using the older slf4j 1.x and javax.servlet APIs a bundle with the ‘legacy’ classifier is built.

This bundle is not included in the feature model used for local development and integration tests and needs to be deployed manually in the applications that consume it.