Added MCp support
This commit is contained in:
@@ -41,7 +41,14 @@ The application follows a modular, hierarchical architecture where high-level fu
|
||||
### **5. Notifications & Platform Services**
|
||||
* Multi-channel delivery engine (`NotificationPlatform`) tracking candidate invitations, reminders, and status updates (`NotificationStatus`) across Email, SMS, WhatsApp, In-App, and Webhooks.
|
||||
|
||||
### **6. Background Processing & Distributed Jobs Engine**
|
||||
### **6. Model Context Protocol (MCP) — In-App & External Tooling**
|
||||
* **Central Tool Definitions (`PostFundManagement.Application/Mcp`)**: Tools proxy core domain services organized by business domain (`Grants`, `Projects`, `Execution`, `Governance`, `Evidence`, `Communications`, `Users`).
|
||||
* **In-App MCP (`PostFundManagement.Api`)**: The API has direct in-process access to tooling via `IInAppMcpClient` without making external web or HTTP calls.
|
||||
* **External MCP Server (`PostFundManagement.Mcp`)**: Dedicated .NET 10 host serving MCP tools over HTTP/SSE (`/mcp`) and Stdio (`--stdio`) for external agents, Claude Desktop, and IDEs.
|
||||
* **Token Optimization**: Standardized `McpToolResult` models minimize prompt token overhead.
|
||||
* **Agent Status**: Tooling infrastructure is established; agent definitions are deferred to future milestones.
|
||||
|
||||
### **7. Background Processing & Distributed Jobs Engine**
|
||||
* **`PostFundManagement.Jobs`**: Dedicated background execution host powered by **Quartz.NET (v4.6+)** with a PostgreSQL clustered JobStore (`pfm-scheduler`).
|
||||
* **Decoupled Architecture**: `PostFundManagement.Api` serves strictly as a scheduler client (`ZeroSizeThreadPool`), dispatching events into the cluster while leaving execution exclusively to `PostFundManagement.Jobs` (`MaxConcurrency = 5`).
|
||||
* **Event-Driven Execution**: Domain events implementing `IEvent : INotification` are mediated and serialized into `MediatorJob<TNotification>`.
|
||||
|
||||
Reference in New Issue
Block a user