mcp-odoo-architect
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| draft_planA | Turn a business requirement into a reviewable 4-section Odoo addon architecture plan (scope, model, views/access, quality gate). |
| generate_addonA | Generate an 11-file Odoo addon starter (manifest, models, views, security, tests, README) composed from the requirement. Starter only — review + staging install before production. |
| validate_addonA | Run the 7 static checks (module name, manifest deps, ORM use, XML, access rights, tests, guardrails) over generated files. |
| explain_tradeoffsC | Explain risks, rejected alternatives, and why the plan is upgrade-safe. |
| list_presetsA | List the 4 built-in demo briefs (urgency, pharmacy, POS discount, Shopify bridge). |
| save_addonB | Generate the starter and write all files to output_dir// on disk. Returns directory, tree, and validation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.