#7529 ticket md files

Author: tobiu

.github/ISSUE/epic-agent-managed-databases.md

@@ -0,0 +1,18 @@
+---
+title: "Epic: Implement Agent-Managed Database Tools"
+labels: epic, AI
+---
+
+GH ticket id: #7529
+
+**Assignee:** tobiu
+**Status:** To Do
+
+## Scope
+
+Enhance the `knowledge-base` and `memory-core` MCP servers with tools that allow an AI agent to start and stop their respective ChromaDB instances. The servers will still connect to pre-existing databases if available, but will now provide the agent with the capability to manage the database lifecycle itself. This hybrid approach offers maximum flexibility for both developers and agents.
+
+## Top-Level Items
+
+- `ticket-kb-add-db-tools.md`: Add `start/stop_database` tools to the Knowledge Base server.
+- `ticket-mc-add-db-tools.md`: Add `start/stop_database` tools to the Memory Core server.

.github/ISSUE/ticket-kb-add-db-tools.md

@@ -0,0 +1,23 @@
+---
+title: "Add Database Management Tools to Knowledge Base Server"
+labels: enhancement, AI
+---
+
+Parent epic: #7529
+GH ticket id: #7530
+
+**Phase:** 1
+**Assignee:** tobiu
+**Status:** To Do
+
+## Description
+
+To give agents more control over their environment, we will add tools to the Knowledge Base server to start and stop its underlying ChromaDB instance.
+
+## Acceptance Criteria
+
+1.  A `start_database` tool is added to the `knowledge-base` server's `openapi.yaml`.
+2.  The tool's service handler executes `chroma run --path ./chroma` as a background process.
+3.  A `stop_database` tool is added, which can terminate the process started by `start_database`.
+4.  The `healthcheck` tool is updated to include the running status of the database process.
+5.  The new tools are implemented in a new `databaseLifecycleService.mjs`.

.github/ISSUE/ticket-mc-add-db-tools.md

@@ -0,0 +1,23 @@
+---
+title: "Add Database Management Tools to Memory Core Server"
+labels: enhancement, AI
+---
+
+Parent epic: #7529
+GH ticket id: #7531
+
+**Phase:** 1
+**Assignee:** tobiu
+**Status:** To Do
+
+## Description
+
+To give agents more control over their environment, we will add tools to the Memory Core server to start and stop its underlying ChromaDB instance.
+
+## Acceptance Criteria
+
+1.  A `start_database` tool is added to the `memory-core` server's `openapi.yaml`.
+2.  The tool's service handler executes `chroma run --path ./chroma-memory --port 8001` as a background process.
+3.  A `stop_database` tool is added, which can terminate the process started by `start_database`.
+4.  The `healthcheck` tool is updated to include the running status of the database process.
+5.  The new tools are implemented in a new `databaseLifecycleService.mjs`.