Added MCp support

Architecture.md

@@ -16,6 +16,8 @@ The PFM platform is constructed using **Clean Architecture** and **Domain-Driven
 │  PostFundManagement.ConsoleUI      │  PostFundManagement.PartnerUI     │
 │  (Internal Staff & Governance)     │  (External Recipient Portal)      │
 │  React 19 + TypeScript + Vite      │  React 19 + WebGL (OGL) + Vite    │
+│                                    │                                   │
+│  PostFundManagement.Mcp (External MCP Server Host - HTTP/SSE & Stdio)  │
 └───────────────────────────────────┬────────────────────────────────────┘
                                     │ HTTPS / REST (v1/api/*) + OIDC PKCE
 ┌───────────────────────────────────▼────────────────────────────────────┐
@@ -316,3 +318,24 @@ The background job runner powers four essential operational workloads:
 
 
 
+
+
+---
+
+## 11. Model Context Protocol (MCP) Architectural Specification
+
+### 11.1 Architectural Shift & Philosophy
+The PFM platform integrates the **Model Context Protocol (MCP)** standard (v2.3.0) to expose domain capabilities both internally and externally while preventing token exhaustion and eliminating network call overhead:
+
+1. **Dual Realisation Pattern**:
+   * **In-App MCP (`PostFundManagement.Api`)**: Internal features, handlers, and workflows obtain in-process access to MCP tooling via `IInAppMcpClient`. Calls are executed directly against scoped services with zero network latency, zero serialization overhead, and no external web requests.
+   * **External MCP Server (`PostFundManagement.Mcp`)**: A dedicated standalone presentation host exposes the exact same tools over standard external transports (HTTP/SSE at `/mcp` and command-line Stdio via `--stdio`) for external LLMs, agentic workbenches, and client IDEs.
+
+2. **Application.Services Proxying Pattern**:
+   All tools reside in `PostFundManagement.Application/Mcp` and proxy established `Application.Services` interfaces (`IGrantsService`, `IProjectService`, `IExecutionService`, `IGovernanceService`, `IEvidenceService`, `ICommunicationsService`, `IUserService`). This ensures:
+   * **Single Source of Truth (BR-005)**: Business validation, entity mapping, and audit logging happen identically whether called from an HTTP endpoint, an internal in-app MCP consumer, or an external MCP server.
+   * **Domain Groupings**: Tools are partitioned by service domains (`Grants`, `Projects`, `Execution`, `Governance`, `Evidence`, `Communications`, `Users`), providing clean tool namespaces (e.g., `grants_create_award`, `execution_approve_disbursement`).
+   * **Token Usage Optimization**: Responses are wrapped in concise `McpToolResult<T>` records, filtering out internal framework metadata and returning concise JSON structures to minimize LLM context window consumption.
+
+3. **Current Agentic Boundary**:
+   The platform establishes the full tooling layer and in-app client contracts; no autonomous agents are defined in this release, preserving clear architectural boundaries for scheduled future agent implementations.