PU

pratikjadhav2726/unified-mcp-tool-graph

Developer tools

이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기

28 stars 7 forks 품질 51 트렌드 11MIT

Instead of dumping 1000+ tools into a model’s prompt and expecting it to choose wisely, the Unified MCP Tool Graph equips your LLM with structure, clarity, and relevance.

개요

is a research-driven project that aggregates and structures tool APIs from diverse into a centralized . This graph functions as an intelligent infrastructure layer that enables and to the most relevant tools for any task — without being overwhelmed by redundant or confusing options. Dynamic MCP Server Spin-Up & Minimal Tool Context - The system now . Five popular MCP servers (including the Dynamic Tool Retriever MCP) are kept warm by default; others are started on demand and kept alive for 10 minutes after last use. - returns not just tool metadata, but also the config needed to run/connect to the MCP server for each tool (fetched from the vendor's GitHub README automatically). - Uses the vendor's GitHub repo to extract the MCP server config (from README) for each tool, so agents can spin up/connect to the right server on the fly. - If config extraction fails, the system logs a warning and continues, ensuring robust tool retrieval. - (not all tools from all MCP servers).

README

원문 README의 일부입니다. 원문 보기.

Unified MCP Tool Graph: A Intelligence Layer for Dynamic Tool Retrieval

Unified MCP Tool Graph is a research-driven project that aggregates and structures tool APIs from diverse Model Context Protocol (MCP) servers into a centralized Neo4j graph database. This graph functions as an intelligent infrastructure layer that enables large language models (LLMs) and agentic AI systems to dynamically retrieve the most relevant tools for any task — without being overwhelmed by redundant or confusing options.


🚀 Recent Updates: This has been integrated into SmarterMCP in the preview mode.

Dynamic MCP Server Spin-Up & Minimal Tool Context

🟢 Dynamic MCP Server Orchestration

  • The system now spins up only the MCP servers required for a given user query. Five popular MCP servers (including the Dynamic Tool Retriever MCP) are kept warm by default; others are started on demand and kept alive for 10 minutes after last use.
  • Dynamic Tool Retriever MCP returns not just tool metadata, but also the config needed to run/connect to the MCP server for each tool (fetched from the vendor’s GitHub README automatically).
  • Automatic MCP Config Extraction: Uses the vendor’s GitHub repo to extract the MCP server config (from README) for each tool, so agents can spin up/connect to the right server on the fly.
  • Error Handling: If config extraction fails, the system logs a warning and continues, ensuring robust tool retrieval.

🟢 Minimal Tool Context for LLMs/Agents

  • Only the exact tools required for the user query are loaded into the agent’s context (not all tools from all MCP servers). This prevents LLM confusion and infinite tool loops.
  • End-to-End Flow:
    1. User query is received.
    2. Dynamic Tool Retriever MCP queries the Neo4j graph and returns the top relevant tools plus their MCP server configs.
    3. The agent spins up/connects to only the required MCP servers (using the configs), and loads only the retrieved tools.
    4. The agent executes the workflow and returns the answer.

🟢 A2A and LangGraph Agent Support

  • A2A Agent Example: See Example_Agents/A2A_DynamicToolAgent/ for a fully dynamic A2A agent that orchestrates MCP servers and tools per request.
  • LangGraph Example: See Example_Agents/Langgraph/ for a LangGraph agent using the same dynamic, minimal-tool approach.

🔬 This repository focuses on the creation and evolution of the Unified Tool Graph Database. Chatbot-based integration (e.g., LangChain) is treated as a modular extension of this foundational layer.

📢 Support for Cline, IDE’s coming soon…


Research Problem

GitHub에서 전체 README 보기

설치

This server does not publish a one-line install command.

Open the repository installation guide MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →