mcp-odoo-architect
Related Servers
Alternatives to mcp-odoo-architect
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables local, offline inspection and analysis of agentic AI projects by scanning project structure, detecting agent tools, and generating architecture reports through MCP tools, resources, and prompts.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to generate complete, runnable MCP server projects from natural-language tool descriptions, including schema, implementation, tests, README, and license.MIT
- AlicenseNot gradedqualityAmaintenanceAI-powered Odoo engineering platform providing static analysis, domain knowledge, and 14 MCP tools for code review, model exploration, and security auditing of Odoo modules.18 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables offline AI agent automation with embedded local LLM (Qwen 2.5), sandboxed file operations through AgentFS, and dynamic skill loading. Exposes capabilities via MCP with tri-state safety guards for private, air-gapped environments without network connectivity or API costs.-
- AlicenseNot gradedqualityAmaintenanceLocal MCP server that gives AI agents a project constitution (LAWS.md), a code graph (Compass), and a spec-driven workflow — all 100% local with no LLM or cloud.33 npm1MIT
- AlicenseAqualityCmaintenanceGenerates production-ready MCP servers with dual-mode (MCP + CLI) architecture, tests, and documentation. Includes progressive disclosure tools for AI agents and best practices guidance.7Apache 2.0
TDQS
Scored across 6 tools
Each tool has a distinct role in the architecture workflow: planning, generating, validating, explaining, listing presets, and saving. The only minor overlap is generate_addon and save_addon, since both trigger generation, but the descriptions clearly separate in-memory output from disk persistence.
All tool names follow a consistent snake_case verb_noun pattern: draft_plan, generate_addon, validate_addon, explain_tradeoffs, list_presets, save_addon. This makes the tool set predictable and easy for an agent to navigate.
With 6 tools, the server is well-scoped for an Odoo addon architecture and scaffolding workflow. Each tool earns its place and the count is neither too thin nor bloated.
The workflow is covered end-to-end: draft a plan, generate the starter addon, validate it, save it to disk, understand tradeoffs, and use presets for quick starts. There are no obvious dead ends for the stated purpose of producing a reviewable Odoo addon starter.