sling-org-apache-sling

Apache Sling MCP Server provides a remote MCP (Model Context Protocol) endpoint for integrating with coding assistants and AI copilots. This server is built on top of the Sling starter and exposes an MCP API that allows tooling to fetch Sling-specific context, bundles, and content to assist with development and automation tasks. To use it, first start the server using the Maven commands described in the installation section; the server will be available at http://localhost:8080/mcp for remote connections. In your coding assistant, configure a remote MCP server pointing to that URL, then begin querying for Sling resources, bundles, and OSGi context information as needed by your tooling.

Once running, you can leverage the MCP server to explore Sling-specific APIs, OSGi bundles, content repositories, and configuration data. Some typical capabilities you might use include retrieving bundle metadata, querying service references, inspecting Sling Resource Resolutions, and integrating with Whiteboard-contributed MCP components to extend the available endpoints.

To connect your tool: add a remote MCP server with location http://localhost:8080/mcp and use the provided MCP endpoints to request information about Sling modules, configurations, and runtime state. The server uses the Sling Whiteboard contributions as a basis for the MCP endpoints, so expect endpoints related to mcp-server-contributions for enhanced functionality.

Prerequisites:

• Java Development Kit (JDK) 8 or newer
• Apache Maven installed and available on PATH
• Optional: Sling starter environment if you want to run within a Sling-based context

Installation steps:

1. Ensure Java and Maven are installed

   • Verify Java: java -version
   • Verify Maven: mvn -version

2. Build and start the MCP server using Maven

   • Run the commands from the README to build and start: mvn install feature-launcher:start feature-launcher:stop -Dfeature-launcher.waitForInput
   • This starts the MCP server endpoint used by tooling at http://localhost:8080/mcp

3. Install and deploy the MCP server contributions bundle (optional but recommended)

   • Build and install the contributions bundle included in Sling Whiteboard: mvn -f whiteboard/mcp-server-contributions/ install sling:install

4. Connect your coding assistant tool to the MCP server

   • In your tool, configure a remote MCP server with location http://localhost:8080/mcp

Prerequisites recap:

• JDK installed
• Maven installed
• Sufficient network permissions to run and expose port 8080
• Optional Sling Whiteboard contributions for enhanced MCP endpoints

Notes and tips:

• The MCP server is intended to be run in a development or test environment aligned with a Sling Starter setup. The port 8080 should be open for tooling to connect.
• If you encounter port or startup issues, verify that no other process is occupying port 8080 and that Maven can access the necessary repositories.
• The legacy classifier mentioned in the README refers to older SLF4J/servlet configurations; this MCP server primarily targets current Sling Starter usage.
• The exact MCP endpoints may be augmented by the Sling Whiteboard contributions; ensure you have installed those artifacts if you rely on extended MCP features.