Data is not actually imported or copied from transactional systems into LegalFab's storage - only metadata is synchronized with the Knowledge Fabric. The actual data remains in your source systems, while the Knowledge Fabric maintains up-to-date metadata catalogs, providing unified access and governance without data replication. Metadata synchronization frequency is configurable based on your needs but typically runs continuously or at short intervals to ensure the fabric's catalog reflects the current schema and data availability. This approach eliminates batch import windows, data staleness issues, and the storage costs associated with copying large volumes of transactional data. When the system needs to access actual case data or documents, it queries the source systems directly using the metadata mappings maintained in the Knowledge Fabric.

LegalFab takes an MCP-first approach to data integration, leveraging Model Context Protocol as the primary strategy for connecting to systems with limited or absent APIs. MCP servers act as intelligent intermediaries between LegalFab's AI components and your legal systems, providing secure, standardized access to data without requiring the source systems to expose traditional REST APIs. This MCP-native architecture is particularly powerful for real-time workflows because it enables the AI to pull relevant data on demand rather than requiring pre-configured ETL pipelines or API endpoints. Complementary strategies include direct database connections for high-volume data access, event bridges for change notifications, and the Dataflow Pipes component for batch processing when appropriate. The MCP-first approach modernizes integration with legacy systems by making them AI-accessible without the need for expensive API development or middleware, while maintaining security and governance through the Knowledge Fabric layer.

Does LegalFab provide an alternative to traditional API or direct SQL access for these scenarios?

Yes, LegalFab's MCP-first architecture provides a modern alternative to traditional API or direct SQL access for data integration. Model Context Protocol enables AI-native data access for MCP servers that wrap your existing systems - legacy databases, file systems, or applications - without requiring you to build and maintain custom REST APIs or write complex SQL queries. MCP servers expose data contextually to LegalFab's AI components in a standardized, semantic way that's designed for intelligent retrieval rather than rigid endpoint definitions. Business users can configure MCP connections through the Knowledge Fabric interface by defining the data entities and relationships, rather than coding integration logic or managing database schemas directly. For scenarios that require additional orchestration, the Dataflow Pipes component complements MCP by handling batch processing, scheduled extractions, and complex transformations, while MCP serves as the primary integration layer for AI-powered workflows.