What distinguishes this architecture from direct LLM–database interaction?
All data access must pass through the MCP broker as a “tool”, enforcing a strict separation between semantic processing (LLM) and data retrieval (agent).
@jaimealruiz
Basic information
Diseño e Implementación de interconexión entre LLM y Espacios de Datos mediante Model Context Protocol (MCP)
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
This project documents a Final Degree Project (TFG) that designs and implements a multi-agent architecture interconnecting data spaces and generative AI. It uses a broker based on the Model Context Protocol (MCP) combined with the Google A2A (Agent to Agent) protocol, enabling structured communication between LLM agents and a local data space.
The system is deployed via Docker Compose. Agents register with the MCP broker on startup using a POST request to /agent/register. A command‑line client script (consola) sends natural‑language questions to the LLM agent, which generates SQL and coordinates the query cycle. Configuration is managed through a .env file with fixed agent IDs.
All data access must pass through the MCP broker as a “tool”, enforcing a strict separation between semantic processing (LLM) and data retrieval (agent).
The system uses Docker Compose, DuckDB, FastAPI, and Transformer’s TinyLlama-1.1B-Chat-v1.0. No external cloud dependencies are needed.
Data is stored locally in a DuckDB file (`lake.duckdb`) containing the table `iceberg_space.ventas`. It is loaded via the `load_data.py` script.
The current implementation is a local prototype. Future work includes adopting full Google A2A specifications (Agent Card, JSON‑RPC 2.0, SSE), persisting messages and agents to a database, and adding conversation IDs for traceability.
Agents register at startup with a fixed `agent_id` from the `.env` file (or an auto‑generated one). The broker maintains a registry in memory.

Couples therapist Figs O'Sullivan (LMFT, 17 years, endorsed by Sue Johnson, creator of EFT) inside your AI. Ask relationship questions answered from his clinical writing, name the pattern in a fight, get a three-step rep

Request dedicated senior developers to work on your project, write job descriptions, and prep technical interviews — all without leaving your Claude chat. Just describe what you need, and Lemon.io MCP does the rest. 1–3
A curated list of references for MLOps

Connect your AI assistant to your own YOUB endurance training account. Read recorded activities with full analysis, planned sessions, race goals, wellness (HRV, sleep, resting HR) and your athletic profile. Create or mov
不止于 CSS
Comments