Provides architecture mapping for Python projects, identifying monorepo/multiproject layouts and exposing source modules and folder structure.
Provides architecture mapping for React codebases, exposing project type, modules, and top-level source directories such as components and hooks.
Provides architecture mapping for Rust projects, identifying project type and exposing module and source-folder structure.
Provides architecture mapping for Symfony projects, identifying project type and exposing module and source-folder structure.
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., "@Universal Architecture Context MCP Server what modules does this project have?"
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.
Un servidor Model Context Protocol (MCP) ligero, dinámico y totalmente universal. Está diseñado para mapear y transmitir la estructura de arquitectura de cualquier proyecto de software a asistentes de IA (como OpenCode), reduciendo hasta un 90% el consumo de tokens al evitar la exploración recursiva e individual de archivos.
🧠 Agnóstico y Universal: Compatible con Symfony, React, Node, Go, Rust, Python, Java, C#, etc.
🏢 Autodetección de Arquitectura: Reconoce automáticamente si el repositorio es un monolito o un monorepo/multiproyecto (ej. proyect-api y proyect-front).
📂 Clasificación Dinámica: Inspecciona el directorio de código fuente (src, app, lib, pkg) y agrupa los archivos según su carpeta de primer nivel (componentes, controladores, entidades, hooks, utils, etc.).
🪟 Cross-Platform: Soporte nativo y normalización de rutas para Windows, macOS y Linux.
Related MCP server: spring-api-intel-mcp
Herramienta | Parámetros | Descripción |
| Ninguno | Devuelve el tipo de arquitectura detectada (monolito o multiproyecto) y la lista de módulos/subproyectos encontrados. |
|
| Devuelve la estructura dinámica de carpetas y archivos. Si no se indica |
Clonar/Ubicar el repositorio en tu proyecto:
cd mcp-architecture-contextDevuelve la estructura de carpetas y archivos. Si no se indica 'module', devuelve la estructura completa de todo el proyecto.
Inputs: module.
Lista todos los módulos/subproyectos detectados en el repositorio y su tipo de arquitectura (monolito o multiproyecto).
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
Only two tools with clearly distinct purposes: one lists modules and their architecture types, the other returns file/folder structure. No overlap in functionality.
Both tool names follow a consistent verb_noun pattern: list_modules and get_project_structure. The verbs (list, get) and nouns (modules, project_structure) are clear and predictable.
With only 2 tools, the server feels thin for a domain as broad as 'Universal Architecture Context'. While each tool is useful, the set is borderline minimal and might benefit from additional tools like get_module_details or get_dependencies.
The two tools cover basic inspection (modules and structure) but miss significant aspects of architecture analysis such as dependency graphs, architectural pattern detection, or per-module configuration details. For a server claiming 'Universal Architecture Context', the surface is notably incomplete.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Project memory, documentation and controlled secret access for AI coding agents.
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
Code-map tools for AI agents: see a repo's structure first, then edit only what matters.
