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
commit 4c0cc21cf2f79bff95fab36887b4df1265d2b5ac Author: Robert Munteanu <[email protected]> AuthorDate: Wed Dec 10 16:30:15 2025 +0100 chore(mcp): document limitations of the internal API --- .../org/apache/sling/mcp/server/impl/McpServerContribution.java | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/main/java/org/apache/sling/mcp/server/impl/McpServerContribution.java b/src/main/java/org/apache/sling/mcp/server/impl/McpServerContribution.java index 4e3168d..ea15572 100644 --- a/src/main/java/org/apache/sling/mcp/server/impl/McpServerContribution.java +++ b/src/main/java/org/apache/sling/mcp/server/impl/McpServerContribution.java @@ -26,8 +26,14 @@ import io.modelcontextprotocol.server.McpStatelessServerFeatures.SyncResourceSpe import io.modelcontextprotocol.server.McpStatelessServerFeatures.SyncResourceTemplateSpecification; import io.modelcontextprotocol.server.McpStatelessServerFeatures.SyncToolSpecification; +// Temporary abstraction to make it easier to contribute various MCP server features +// +// The major problem with this approach is that all contributions are loaded once the MCPServlet +// is activated and therefore it does not take into account added/changed/removed contributions +// +// Expect this abstraction to change public interface McpServerContribution { - + default Optional<SyncToolSpecification> getSyncToolSpecification() { return Optional.empty(); }
