This ticket covers the implementation of the toolService.mjs for the new AI Knowledge Base MCP server. The implementation will be adapted from the existing toolService.mjs in the github-workflow server.
The goal is to create the service that dynamically parses the openapi.yaml file, builds Zod schemas for validation, and maps operationIds to handler functions.
Acceptance Criteria
- The file
ai/mcp/server/knowledge-base/services/toolService.mjs is created.
- The logic is adapted from
ai/mcp/server/github-workflow/services/toolService.mjs.
- It correctly reads
ai/mcp/server/knowledge-base/openapi.yaml.
- A
serviceMapping object is created, mapping the operationIds from the OpenAPI spec to service functions.
- For this initial ticket, the mapped service functions can be placeholders/dummies (e.g.,
() => Promise.resolve('Not implemented yet')).
- The module exports
listTools and callTool functions that are ready for integration with mcp-stdio.mjs.
This ticket covers the implementation of the
toolService.mjsfor the new AI Knowledge Base MCP server. The implementation will be adapted from the existingtoolService.mjsin thegithub-workflowserver.The goal is to create the service that dynamically parses the
openapi.yamlfile, builds Zod schemas for validation, and mapsoperationIds to handler functions.Acceptance Criteria
ai/mcp/server/knowledge-base/services/toolService.mjsis created.ai/mcp/server/github-workflow/services/toolService.mjs.ai/mcp/server/knowledge-base/openapi.yaml.serviceMappingobject is created, mapping theoperationIds from the OpenAPI spec to service functions.() => Promise.resolve('Not implemented yet')).listToolsandcallToolfunctions that are ready for integration withmcp-stdio.mjs.