David Snelling
2e8e947adc
### Changes: - **Core MCP Components**: - Introduced `BrainyMCPAdapter`, `BrainyMCPService`, and `MCPAugmentationToolset` for handling data access, tool execution, system information, and authentication via MCP. - Added asynchronous handlers to process requests for Brainy data, augmentations, and relationships. - Built pipelines to expose Brainy augmentation capabilities as tools. - **Server Implementations**: - Added WebSocket and REST interfaces in `initializeMCPService` for external MCP requests. - Included rate limiting, authentication, and CORS support for REST API. - **Type Definitions**: - Defined MCP-related types such as `MCPRequestType`, `MCPResponse`, and `MCPToolExecutionRequest` in `src/types/mcpTypes.ts`. - Incorporated augmentation-type-specific methods from `augmentationPipeline`. - **Exports**: - Exposed MCP modules (`BrainyMCPAdapter`, `BrainyMCPService`, `MCPAugmentationToolset`) via `src/mcp/index.ts`. ### Purpose: Introduced a Model Control Protocol (MCP) framework to enable seamless integration of Brainy data and augmentation tools with external models. The implementation provides structured, scalable access to data and tools through both WebSocket and REST APIs.
19 lines
640 B
TypeScript
19 lines
640 B
TypeScript
/**
|
|
* Model Control Protocol (MCP) for Brainy
|
|
*
|
|
* This module provides a Model Control Protocol (MCP) implementation for Brainy,
|
|
* allowing external models to access Brainy data and use the augmentation pipeline as tools.
|
|
*/
|
|
|
|
// Import and re-export the MCP components
|
|
import { BrainyMCPAdapter } from './brainyMCPAdapter.js'
|
|
import { MCPAugmentationToolset } from './mcpAugmentationToolset.js'
|
|
import { BrainyMCPService } from './brainyMCPService.js'
|
|
|
|
// Export the MCP components
|
|
export { BrainyMCPAdapter }
|
|
export { MCPAugmentationToolset }
|
|
export { BrainyMCPService }
|
|
|
|
// Export the MCP types
|
|
export * from '../types/mcpTypes.js'
|