luigidemasi opened a new issue, #54: URL: https://github.com/apache/camel-kit/issues/54
> Imported from [luigidemasi/camel-kit#93](https://github.com/luigidemasi/camel-kit/issues/93), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-23. > Closed by [luigidemasi/camel-kit#100](https://github.com/luigidemasi/camel-kit/pull/100), merged on 2026-06-23. --- ## Description Generated MCP configs currently allowlist Knowledge MCP tools that are not implemented by the Knowledge MCP server. `DefaultGenerator` builds a Knowledge tool list containing: - `camel_docs_component_info` - `camel_docs_search` - `camel_docs_jira_lookup` - `camel_docs_cve_search` - `camel_docs_bugfix_search` - `camel_docs_release_info` - `camel_docs_supported_configs` But `KnowledgeMcpServer` currently implements five tools: - `camel_docs_component_info` - `camel_docs_search` - `camel_docs_cve_search` - `camel_docs_release_info` - `camel_docs_jira_lookup` This can confuse agents and produce tool-call failures for `camel_docs_bugfix_search` and `camel_docs_supported_configs`. ## Expected Behavior Generated MCP configs should allowlist only tools that the Knowledge MCP server actually implements. ## Actual Behavior The generated allowlist includes two non-existent tools. ## Proposed Solution Either: 1. remove `camel_docs_bugfix_search` and `camel_docs_supported_configs` from generated configs, or 2. implement those tools in `KnowledgeMcpServer` if they are still intended product features. ADR-0016 appears to indicate the community Knowledge layer intentionally has five tools, so removing the stale allowlist entries is probably the smaller fix. ## Acceptance Criteria - [ ] Generated MCP config contains only implemented Knowledge MCP tools - [ ] Add a test that compares `DefaultGenerator` Knowledge tool allowlist with `KnowledgeMcpServer` tool methods - [ ] Update docs/templates if they mention removed Knowledge MCP tools -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
