manufacturing-graphrag
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., "@manufacturing-graphragWhich critical defects are blocking the EV BMS release?"
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.
Manufacturing Traceability Intelligence Platform
GraphRAG-powered agentic AI platform for manufacturing traceability using Neo4j, Amazon Bedrock, and MCP.
Architecture
┌─────────────────────────────────────────────────────────────────────┐
│ INGESTION & ENRICHMENT LAYER │
│ Connectors → Chunking → Embeddings → Entity Extraction → │
│ Entity Resolution → Graph Construction │
└──────────────────────────┬──────────────────────────────────────────┘
│
┌──────────────────────────▼──────────────────────────────────────────┐
│ KNOWLEDGE GRAPH (Neo4j) │
│ Product → Requirement → Component → TestCase → TestRun → │
│ Defect → ChangeRequest │
└──────────────────────────┬──────────────────────────────────────────┘
│
┌──────────────────────────▼──────────────────────────────────────────┐
│ RETRIEVAL LAYER │
│ VectorRetriever │ GraphRAGRetriever │ NL2CypherRetriever │ Hybrid │
└──────────────────────────┬──────────────────────────────────────────┘
│
┌──────────────────────────▼──────────────────────────────────────────┐
│ AGENT LAYER │
│ LangGraph Agent (plan→retrieve→reason→validate→respond) │
│ Strands Agent (tool-calling with 5 specialized graph tools) │
└──────────────────────────┬──────────────────────────────────────────┘
│
┌──────────────────────────▼──────────────────────────────────────────┐
│ INTERFACE LAYER │
│ FastAPI REST │ MCP Server (Claude Desktop / Cursor compatible) │
└─────────────────────────────────────────────────────────────────────┘Related MCP server: GraphRAG MCP
Quick Start
1. Prerequisites
Neo4j 5.x (with APOC plugin)
Python 3.11+
AWS credentials with Bedrock access (Claude 3.5 Sonnet + Titan Embed v2)
2. Setup
cd manufacturing-graphrag
python -m venv .venv
.venv\Scripts\activate # Windows
pip install -r requirements.txt
python -m spacy download en_core_web_sm
copy .env.example .env # Edit with your credentials3. Start Neo4j (Docker)
docker-compose up neo4j -d4. Seed the Knowledge Graph
set PYTHONPATH=src
python scripts/seed_data.py5. Start the Platform
# API server
python main.py api
# MCP server (for Claude Desktop)
python main.py mcp
# Both
python main.py all6. Ingest Documents
python scripts/ingest.py path/to/spec.pdf path/to/requirements.csvAPI Endpoints
Method | Endpoint | Description |
GET |
| Health check |
GET |
| Node counts by label |
POST |
| Upload and ingest a document |
POST |
| Ingest a structured API record |
POST |
| Hybrid GraphRAG query |
POST |
| LangGraph reasoning agent |
POST |
| Strands tool-calling agent |
GET |
| Full defect traceability chain |
GET |
| Product traceability summary |
Example Queries
# Hybrid GraphRAG query
curl -X POST http://localhost:8000/query \
-H "Content-Type: application/json" \
-d '{"question": "What components are affected by the thermal runaway defect?"}'
# LangGraph agent — multi-step reasoning
curl -X POST http://localhost:8000/agent/langgraph \
-d '{"question": "Trace the full impact chain of DEF-001 and identify all change requests needed"}'
# Strands agent — tool-calling
curl -X POST http://localhost:8000/agent/strands \
-d '{"question": "Which critical defects are blocking the EV BMS release?"}'
# Defect traceability
curl http://localhost:8000/traceability/defect/DEF-002MCP Integration (Claude Desktop)
Copy config/claude_desktop_mcp.json content into your Claude Desktop claude_desktop_config.json.
Available MCP tools:
ask_manufacturing_ai— hybrid GraphRAG Q&Asemantic_search— vector similarity searchgraph_trace— graph traversal retrievalnatural_language_to_cypher— NL2Cypherget_defect_chain— full defect traceabilityget_requirement_traceability— requirement coverageproduct_health_dashboard— product metrics
Knowledge Graph Schema
(Product)-[:HAS_REQUIREMENT]->(Requirement)
(Component)-[:IMPLEMENTS]->(Requirement)
(TestCase)-[:VALIDATES]->(Requirement)
(TestRun)-[:INSTANCE_OF]->(TestCase)
(TestRun)-[:FOUND_IN]->(Defect)
(Defect)-[:AFFECTS]->(Component)
(Defect)-[:TRIGGERS_CHANGE]->(ChangeRequest)
(ChangeRequest)-[:MODIFIES]->(Component)
(Document)-[:CONTAINS_CHUNK]->(Chunk)
(Chunk)-[:MENTIONS]->(any entity)Running Tests
set PYTHONPATH=src
pytest tests/ -vThis server cannot be deployed
Maintenance
Related MCP Connectors
Natural-language queries over a verified emissions knowledge graph, plus standards validation
Knowledge graph ingestion, entity search, ontology analysis, and CoSync scoring.
Shared semantic graph for AI reviews, classification and structured memory across AI assistants.
AI knowledge graph for architecture, portfolio, and digital strategy management.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables storage and retrieval of knowledge in a graph database format, allowing users to create, update, search, and delete entities and relationships in a Neo4j-powered knowledge graph through natural language.5-
- FlicenseCqualityDmaintenanceEnables enterprise document retrieval using graph-based reasoning and knowledge graphs. Allows agents to search and extract information from scattered documents through structured entity and relationship extraction.12-
- FlicenseCqualityDmaintenanceCombines a knowledge graph with RAG (Retrieval-Augmented Generation) capabilities for semantic code indexing and search. Enables creating entity relationships, managing observations, and performing semantic searches across indexed codebases.13-
- FlicenseNot gradedqualityCmaintenanceTransforms code repositories and development documentation into a queryable Neo4j knowledge graph, enabling AI assistants to perform intelligent code analysis, dependency mapping, impact assessment, and automated documentation generation across 15+ programming languages.7-