solvro/ml-mcp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
Solvro internal MCP server
概要
Knowledge Graph RAG System for PWr Intelligent assistant for Wrocław University of Science and Technology Quick Start • Architecture • Features • Querying - - Guardrails system determines query relevance - - Converts questions to graph queries - - Retrieval-Augmented Generation with Neo4j - - Standard Model Context Protocol interface - - Optional Langfuse tracing integration - - One command deployment The chat UI and the HTTP API that users talk to live in backend-mcp; this repository is the graph, the retrieval pipeline and the ETL that fills it. Nothing is published on the host. just up-dev layers docker/compose.dev.yml on top, which republishes the ports on 127.0.0.1 for the Neo4j browser, just kg and uv run dump-graph. The heart of the system is a LangGraph-based RAG pipeline that intelligently processes user queries: 1. - Fast LLM determines if query is relevant to knowledge base 2. - Accurate LLM converts natural language to Cypher query 3.
README
以下は原文 README の抜粋です。原文を見る。
SOLVRO MCPWr
Knowledge Graph RAG System for PWr Intelligent assistant for Wrocław University of Science and Technology
Quick Start • Architecture • Features • Querying
backend-mcp (separate repo) │ ml-mcp (this repo, no host ports)
┌─────────────┐ ┌──────────────┐│ ┌─────────────┐ ┌─────────────┐
│ nginx │──▶│ chat-service │┼──▶│ MCP Server │─────────▶│ Neo4j │
│ :8080 │ │ ││ │ :8005 (int.)│ │ :7687 (int.)│
└─────────────┘ └──────────────┘│ └─────────────┘ └─────────────┘
auth + UI agent │ solvro-mcp-internal mcp_network
- Intelligent Query Routing - Guardrails system determines query relevance
- Natural Language to Cypher - Converts questions to graph queries
- Knowledge Graph RAG - Retrieval-Augmented Generation with Neo4j
- MCP Protocol - Standard Model Context Protocol interface
- Observability - Optional Langfuse tracing integration
- Docker Ready - One command deployment
Quick Start
# Setup
just setup
cp .env.example .env # Edit with your API keys
# Run with Docker
just up # Neo4j + MCP Server, reachable only by backend-mcp (no host ports)
just up-dev # same, plus 127.0.0.1 ports for local work
just logs # View logs
just down # Stop services
Architecture
System Overview
backend-mcp (separate repo) │ ml-mcp (this repo, no host ports)
┌─────────────┐ ┌──────────────┐│ ┌─────────────┐ ┌─────────────┐
│ nginx │──▶│ chat-service │┼──▶│ MCP Server │─────────▶│ Neo4j │
│ :8080 │ │ ││ │ :8005 (int.)│ │ :7687 (int.)│
└─────────────┘ └──────────────┘│ └─────────────┘ └─────────────┘
auth + UI agent │ solvro-mcp-internal mcp_network
| Service | Container port | Reachable from | Description |
|---|---|---|---|
mcp-server |
8005 | backend-mcp over solvro-mcp-internal |
FastMCP server exposing knowledge_graph_tool and /health |
neo4j |
7474/7687 | mcp-server over mcp_network only |
Knowledge graph database |
The chat UI and the HTTP API that users talk to live in backend-mcp; this repository is the
graph, the retrieval pipeline and the ETL that fills it.
Nothing is published on the host. just up-dev layers docker/compose.dev.yml on top, which
republishes the ports on 127.0.0.1 for the Neo4j browser, just kg and uv run dump-graph.
RAG Pipeline
The heart of the system is a LangGraph-based RAG pipeline that intelligently processes user queries:
インストール
This server does not publish a one-line install command.
Open the repository installation guide MCP 初心者？mcpskill.org のガイドから始めましょう →