expose manifest-driven project knowledge through MCP

This commit is contained in:
2026-09-29 08:30:38 +01:00
parent 9f61f9c07d
commit 58f11a8123
14 changed files with 665 additions and 13 deletions
@@ -296,9 +296,17 @@ public class StudioApplicationConfiguration {
}
@Bean
p.studio.app.mcp.McpToolRegistry mcpToolRegistry(p.studio.app.mcp.McpToolCatalog catalog, ObjectMapper mapper) {
// Providers are connected in PLN-0139 steps 17–20. Never advertise placeholders.
return new p.studio.app.mcp.McpToolRegistry(catalog, mapper, java.util.Map.of());
p.studio.api.automation.ProjectKnowledge projectKnowledge(
p.studio.core.project.ProjectAccessRegistry projects, ProjectCatalog catalog, ObjectMapper mapper) {
return new p.studio.app.compiler.CompilerProjectKnowledge(projects, catalog, mapper);
}
@Bean
p.studio.app.mcp.McpToolRegistry mcpToolRegistry(p.studio.app.mcp.McpToolCatalog catalog, ObjectMapper mapper,
p.studio.api.automation.ProjectKnowledge knowledge) {
// Further providers are connected in PLN-0139 steps 18–20. Never advertise placeholders.
return new p.studio.app.mcp.McpToolRegistry(catalog, mapper,
p.studio.app.mcp.McpProjectKnowledgeTools.handlers(knowledge, mapper));
}
@Bean(initMethod = "start", destroyMethod = "close")