This is an automated email from the ASF dual-hosted git repository. rombert pushed a commit to branch issue/update-readme in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-mcp-server.git
commit 01ab975d43c76ba71a195d84fb21c16b80da2175 Author: Robert Munteanu <[email protected]> AuthorDate: Wed Mar 25 15:55:29 2026 +0100 chore: readme updates --- README.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ed82a21..b5ec725 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ Experimental MCP Server implementation for Apache Sling. -## Usage +## Development Build the project with Maven and start up the MCP server, based on the Apache Sling Starter: @@ -23,7 +23,7 @@ the configuration can look as follows ```json "aem-cs-sdk": { "type": "streamable-http", - "url": "http://localhost:4502/bin/mcp";, + "url": "http://localhost:8080/bin/mcp";, "headers": { "Authorization": "Basic YWRtaW46YWRtaW4=" } @@ -32,6 +32,20 @@ the configuration can look as follows 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](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](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 classifier with the 'legacy' classifier is built.
