F
licenseNot graded
qualityC
maintenanceEnables users to access, search, and analyze Spark Desktop meeting transcripts and emails through natural language via the Model Context Protocol.
11
-
cfabric-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cfabric-mcpfind all clauses with a verb in Genesis 1"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Overview
Context-Fabric brings corpus analysis into the AI era. Built on the proven Text-Fabric data model, it introduces a memory-mapped architecture enabling parallel processing for production deployments—REST APIs, multi-worker services, and AI agent tools via MCP.
Built for Production — Memory-mapped arrays enable true parallelization. Multiple workers share data instead of duplicating it.
AI-Native — MCP server exposes corpus operations to Claude, GPT, and other LLM-powered tools.
Powerful Data Model — Standoff annotation, graph traversal, pattern search, and arbitrary feature annotations.
Dramatic Efficiency — 3.5x faster loads, 65% less memory in single process, 62% less with parallel workers.
Related MCP server: MCP Server
MCP Server for AI Agents
Context-Fabric includes cfabric-mcp, a Model Context Protocol server that exposes corpus operations to AI agents:
# Start the MCP server
cfabric-mcp --corpus /path/to/bhsa
# Or with SSE transport for remote clients
cfabric-mcp --corpus /path/to/bhsa --sse 8000The server provides 10 tools for discovery, search, and data access—designed for iterative, token-efficient agent workflows.
Memory Efficiency
Text-Fabric loads entire corpora into memory—effective for single-user research, but each parallel worker duplicates that memory footprint. Context-Fabric's memory-mapped arrays change the equation:
Scenario | Memory Reduction |
Single process | 65% less |
4 workers (spawn) | 62% less |
4 workers (fork) | 62% less |
Mean reduction across 10 corpora. Memory measured as total RSS after loading from cache.
Installation
# Core library
pip install context-fabric
# With MCP server
pip install context-fabric[mcp]Quick Start
from cfabric.core import Fabric
# Load a corpus
CF = Fabric(locations='path/to/corpus')
api = CF.load('feature1 feature2')
# Navigate nodes
for node in api.N.walk():
print(api.F.feature1.v(node))
# Traverse structure
embedders = api.L.u(node) # nodes containing this node
embedded = api.L.d(node) # nodes within this node
# Search patterns
results = api.S.search('''
clause
phrase function=Pred
word sp=verb
''')Core API
API | Purpose |
N | Walk nodes in canonical order |
F | Access node features |
E | Access edge features |
L | Navigate locality (up/down the hierarchy) |
T | Retrieve text representations |
S | Search with structural templates |
Performance
Context-Fabric trades one-time compilation cost for dramatic runtime efficiency. Compile once, benefit forever.
Metric | Mean Improvement |
Load time | 3.5x faster |
Memory (single) | 65% less |
Memory (spawn) | 62% less |
Memory (fork) | 62% less |
Mean across 10 corpora. The larger cache enables memory-mapped access—no deserialization, instant loads, shared memory across workers.
Run benchmarks yourself:
pip install context-fabric[benchmarks]
cfabric-bench memory --corpus path/to/corpusPackages
Package | Description |
Core graph engine | |
MCP server for AI agents | |
Performance benchmarking suite |
Links
Citation
If you use Context-Fabric in your research, please cite:
Kingham, Cody. "Carrying Text-Fabric Forward: Context-Fabric and the Scalable Corpus Ecosystem." January 2026.
Authors
Context-Fabric by Cody Kingham, built on Text-Fabric by Dirk Roorda.
License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessUnresponsive
Related MCP Connectors
Shared, permission-aware company context for AI agents, with provenance, approvals and audit.
The BigQuery remote MCP server is a fully managed service that uses the Model Context Protocol to connect AI applications and LLMs to BigQuery data sources. It provides secure, standardized tools for AI agents to list datasets and tables, retrieve schemas, generate and execute SQL queries through natural language, and analyze data—enabling direct access to enterprise analytics data without requiring manual SQL coding.
The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables natural-language querying of structured data via Model Context Protocol, allowing AI agents to answer questions without SQL or API knowledge.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to search, retrieve, and summarize content from workplace tools including Google Drive, Notion, Slack, and Confluence through secure Model Context Protocol.-
- FlicenseAqualityDmaintenanceEnables AI agents to query Fangorn subgraph schemas and conformant data from published data sources via the Model Context Protocol.132-
