Skip to main content
Glama

Related Servers

Alternatives to mcp-odoo-architect

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      A
      maintenance
      Enables ordinary LLMs to be augmented fully offline — with no API keys or external services — through model-aware guardrails, exemplar retrieval, structured self-critique, compliance scoring, and an allowlisted verification runner. Also provides hybrid knowledge-base search, decaying long-term memory, and persistent plan/task management across 54 MCP tools usable from any MCP client such as OpenCode, Claude Desktop, Cursor, or VS Code.
      62
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to generate complete, runnable MCP server projects from natural-language tool descriptions, including schema, implementation, tests, README, and license.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables LLM agents to perform local development and automation over MCP STDIO, including project context retrieval, file read/write and patching, shell/Python execution, Git inspection, work-state tracking, and validation. It runs as a local Python process with Dev and Safe execution modes and audit logging for trusted single-developer environments.
      16
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      AI-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 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.