This is an automated email from the ASF dual-hosted git repository.
rombert pushed a commit to branch master
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-mcp-server.git
The following commit(s) were added to refs/heads/master by this push:
new cf4a72b fix: remove prompts as they pare included in the
contributions bundle (#5)
cf4a72b is described below
commit cf4a72b5126c1c1a03ac41c5948f4ea29c569967
Author: Robert Munteanu <[email protected]>
AuthorDate: Wed Mar 4 13:47:48 2026 +0100
fix: remove prompts as they pare included in the contributions bundle (#5)
Also adjust the README after the move from the whiteboard
---
README.md | 4 +-
bnd.bnd | 2 -
.../libs/sling/mcp/prompts/new-sling-servlet.md | 17 --------
.../libs/sling/mcp/prompts/troubleshoot.md | 45 ----------------------
4 files changed, 2 insertions(+), 66 deletions(-)
diff --git a/README.md b/README.md
index 59b017b..60b78f3 100644
--- a/README.md
+++ b/README.md
@@ -10,10 +10,10 @@ Build the project with Maven and start up the MCP server,
based on the Apache Sl
$ mvn install feature-launcher:start feature-launcher:stop
-Dfeature-launcher.waitForInput
```
-Then build and deploy the sibling contributions package:
+Then build and deploy the [MCP server contributions bundle from the Sling
Whiteboard](https://github.com/apache/sling-whiteboard/tree/master/mcp-server-contributions):
```
-$ mvn -f ../mcp-server-contributions/ install sling:install
+$ 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 .
diff --git a/bnd.bnd b/bnd.bnd
index f1ef54d..c7ccc7c 100644
--- a/bnd.bnd
+++ b/bnd.bnd
@@ -1,5 +1,3 @@
# workaround for https://github.com/modelcontextprotocol/java-sdk/issues/562
Private-Package: io.modelcontextprotocol.json.jackson, \
io.modelcontextprotocol.json.schema.jackson
-
-Sling-Initial-Content:
SLING-INF/libs/sling/mcp/prompts;path:=/libs/sling/mcp/prompts;overwrite:=true
\ No newline at end of file
diff --git
a/src/main/resources/SLING-INF/libs/sling/mcp/prompts/new-sling-servlet.md
b/src/main/resources/SLING-INF/libs/sling/mcp/prompts/new-sling-servlet.md
deleted file mode 100644
index c92cb83..0000000
--- a/src/main/resources/SLING-INF/libs/sling/mcp/prompts/new-sling-servlet.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "Create new Sling Servlet"
-description: "Creates a new Sling Servlet in the current project using
annotations"
-argument.resource-type:
- - title: Resource Type
- - required: true
- - description: The Sling resource type to bind this servlet to
----
-
-# Create a new Sling Servlet
-
- Create a new Sling Servlet for resource type: `{resource-type}`
-
- Use the Sling-specific OSGi declarative services annotations -
`@SlingServletResourceTypes` and `@Component` .
- Configure by default with the GET method and the json extension.
- Provide a basic implementation of the doGet method that returns a JSON
response with a message 'Hello from Sling Servlet at resource type
{resource-type}'.
-
\ No newline at end of file
diff --git
a/src/main/resources/SLING-INF/libs/sling/mcp/prompts/troubleshoot.md
b/src/main/resources/SLING-INF/libs/sling/mcp/prompts/troubleshoot.md
deleted file mode 100644
index d5e9587..0000000
--- a/src/main/resources/SLING-INF/libs/sling/mcp/prompts/troubleshoot.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: "Troubleshooting guide"
-description: "Guide to troubleshoot common issues with Apache Sling
applications"
----
-# Troubleshooting Guide
-
-## Overview
-This guide helps you diagnose and resolve common issues with Apache Sling MCP
Server.
-
-## Common Issues
-
-### MCP Server Not Responding
-- Verify the MCP servlet is registered and active
-- Check OSGi component status
-- Review log files for errors
-
-### Bundle Issues
-- Check bundle state (ACTIVE, RESOLVED, INSTALLED)
-- Verify all dependencies are satisfied
-- Use the OSGi diagnostic tools
-
-### Performance Problems
-- Review recent requests and response times
-- Check system resources
-- Analyze thread dumps if available
-
-### Component Registration Issues
-- Verify component configurations
-- Check service dependencies
-- Review component lifecycle logs
-
-## Diagnostic Tools
-The MCP Server provides several diagnostic tools:
-- Bundle state inspection
-- Component resource analysis
-- Recent request tracking
-- Log file access
-- OSGi diagnostic reports
-
-## Getting Help
-If you continue to experience issues:
-1. Gather diagnostic information using the MCP tools
-2. Review the Apache Sling documentation
-3. Check the Apache Sling mailing lists
-4. File an issue in the Apache Sling JIRA
