Manifold Engine MCP Server
Click 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., "@Manifold Engine MCP Serverindex and analyze the repo for chaos"
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.
Manifold Engine MCP Server
A Model Context Protocol server that gives AI coding assistants high-speed, structural codebase analysis and dynamic context management. Instead of reading code token-by-token, it maps repositories structurally — treating source files as continuous byte-streams, computing structural signatures, and detecting architectural chaos in O(1) time.
Current Status: All Phase 0 critical bugs have been resolved, including FAISS semantic search deserialization,
ingest_reporelative path resolution, combined risk formula transparency, and distinct cluster naming heuristics. All 21 analysis tools are fully functional.
Core Capabilities
Capability | Description |
Structural Indexing | Scans every file into a Valkey-backed grid with compressed signatures and chaos profiles. Sub-millisecond retrieval. |
Chaos Detection | Calculates a |
Dependency & Risk Analysis | Traces import graphs via AST parsing, measures blast radius, combines chaos × blast into a single risk score. |
Working Memory | Inject persistent facts (project conventions, architecture rules) into a Dynamic Semantic Codebook for zero-shot learning. |
Real-Time Sync | Filesystem watcher auto-ingests file saves in milliseconds, keeping the index current without manual re-scans. |
Related MCP server: OpenLore
Installation
Prerequisites
Python 3.10+
Valkey (or Redis) running on
localhost:6379C++20 compiler (for building the native structural engine)
faiss-cpu(required for running thecluster_codebase_structuretool)
Setup
# 1. Start the Valkey backend
valkey-server
# 2. Install the manifold engine
pip install -e .
# 3. Configure your MCP client (Kilo Code, Claude Desktop, Cursor, etc.)Add to your MCP client configuration:
{
"mcpServers": {
"manifold": {
"command": "path/to/virtualenv/bin/python",
"args": ["path/to/SEP-mcp/mcp_server.py"],
"cwd": "path/to/SEP-mcp"
}
}
}Common Workflows & Use Cases
1. New Repository Analysis
When entering a new codebase, execute an initial mapping to immediately understand technical debt distribution.
# 1. Index the repository
ingest_repo (root_dir=".", clear_first=true, compute_chaos=true)
# 2. Verify ingestion was successful
get_index_stats
# 3. Quickly identify the most complex, chaotic files
batch_chaos_scan (pattern="*.py", max_files=30)2. Refactoring Decisions & Sprint Planning
Use the structural risk metrics to objectively decide what code to rewrite.
# 1. Scan for files with BOTH high complexity and high import dependencies
scan_critical_files (pattern="*.py", max_files=10)
# 2. For candidates, predict how soon the file will become unmaintainable
predict_structural_ejection (path="target.py", horizon_days=30)
# 3. For visual confirmation, generate a 4-panel chaos dashboard
visualize_manifold_trajectory (path="target.py")3. Finding Implementation Patterns
Rather than searching by text, search by structural signatures to find similar logic blocks or clones.
# 1. Get the mathematical signature of an existing file
get_file_signature (path="found_file.py")
# 2. Search for any other files that match this structure globally
search_by_structure (signature="c0.213_s0.000_e0.928", tolerance=0.05)4. Continuous Flow
# Run the watcher inside the repo
start_watcher (watch_dir=".")
# The engine now automatically syncs and re-evaluates risk natively whenever files are saved.Tool Reference (20 Tools)
All tools are documented with parameters, examples, and workflows in MCP_TOOL_GUIDE.md.
Indexing & Monitoring
Tool | Purpose | Quick Command |
| Full repository scan into Valkey with signatures and chaos profiles |
|
| Real-time index health: document count, memory, chaos averages |
|
| Background filesystem observer — auto-ingests on file save/delete |
|
File Discovery & Search
Tool | Purpose | Quick Command |
| Browse indexed files by glob pattern |
|
| Read full file content from the Valkey index |
|
| Keyword or regex search across all indexed files with context |
|
| Structural fingerprint (c/s/e) for a file |
|
| Find files with similar structural signatures |
|
| Find files containing a contiguous signature sequence |
|
Chaos Analysis
Tool | Purpose | Quick Command |
| Per-file chaos score, entropy, coherence, collapse risk |
|
| Rank all files by chaos score (highest risk first) |
|
| Forecast when a file becomes unmaintainable |
|
| Generate a 4-panel dashboard of chaos dynamics |
|
| K-Means clustering of files by structural signatures |
|
Dependency & Combined Risk
Tool | Purpose | Quick Command |
| Import dependency tree and impact file count |
|
| Combined risk = 0.6×chaos + 0.4×blast |
|
| Repository-wide scan for highest combined risk |
|
Verification & Memory
Tool | Purpose | Quick Command |
| Compress arbitrary text into manifold signatures |
|
| Check if code structurally matches existing codebase patterns |
|
| Add persistent knowledge to the Dynamic Semantic Codebook |
|
| Remove a previously injected fact |
|
Empirical Validation
React 15.0 Case Study
The structural engine flagged the exact files (ReactReconcileTransaction.js, ReactInstanceHandles.js) that the React core team subsequently deleted and rewrote as React Fiber — without any semantic understanding of JavaScript.
→ Read the study
Langchain ROC Analysis
A blind forward-prediction study on langchain v0.0.300 proved that a chaos score threshold of 0.396 optimally predicts architectural ejection, achieving ~91% of the predictive power of expensive AST-parsing tools at O(1) speed.
→ Read the study
Memory Optimization
Zstandard compression reduced the cpython index from 3.4 GB to 28 MB (>99% reduction) with zero loss in retrieval accuracy.
Documentation
Document | Purpose |
Comprehensive tool reference, workflows, best practices | |
Validation studies and generated reports |
License
MIT — see LICENSE
This server cannot be deployed
Maintenance
Related MCP Connectors
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Codebase graphs, caller impact analysis, and recorded project context for AI coding agents.
Codebase intelligence for AI agents — dead code, blast radius, ownership.
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
Related MCP Servers
- AlicenseAqualityDmaintenanceAnalyzes codebases from local directories, GitHub, and Azure DevOps, providing intelligent context to AI coding assistants through repository structure, critical files, and semantic maps.144MIT
- AlicenseNot gradedqualityAmaintenanceProvides persistent architectural memory and structural cognition for AI coding agents, enabling efficient orientation, graph-aware context, and drift detection across codebase evolution.1,481 npm307MIT
- AlicenseAqualityAmaintenanceProvides AI coding agents with durable architecture memory for repositories by generating structured project maps of responsibilities, relationships, and risks.628 npm1MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding assistants with deep, semantic understanding of local codebases via AST-aware chunking, cross-repo symbol graphs, and architectural memory, enabling context-aware code search and dependency tracing.10MIT