{
"mcpServers": {
"sling-org-apache-sling-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Apache Sling MCP Server
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
Apache-2.0. View license →
Is it maintained?
Last commit 13 days ago. 1 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Sling Org Apache Sling Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Experimental MCP Server implementation for Apache Sling.
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.
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:
mvn packagetarget/slingfeature-tmp/main.json to your own projectFor 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.