Odoo Index MCP
Enables AI agents to search and retrieve details about Odoo code elements (models, fields, views, etc.) with exact file locations using MCP tools.
README
Odoo Index MCP
A lightweight MCP (Model Context Protocol) server for indexing Odoo code elements. Designed to help coding agents quickly look up models, fields, functions, views, and other Odoo components with their exact file locations.
Features
- Fast Indexing: Uses AST parsing for Python and lxml for XML
- Incremental Updates: Only re-indexes changed files (MD5 hash tracking)
- Comprehensive Coverage: Indexes models, fields, methods, views, menus, actions, access rights, rules, scheduled actions, report templates, controller routes, and more
- Multiple References: Tracks all occurrences (definition, inheritance, override, etc.)
- Lightweight: Pure SQLite, no vector DB, no embeddings
- MCP Compatible: Works with Claude Desktop and other MCP clients
What Gets Indexed
Core Elements
- Models: Name, type (regular/transient/abstract), inheritance
- Fields: Name, type, attributes (required, readonly, compute, related, etc.)
- Functions/Methods: Name, decorators (@api.depends, @api.onchange, etc.)
- Views: Type (form/tree/kanban/search), model, inheritance
- Menus: Hierarchy, actions, security groups
- Actions: Type (act_window/server/report), models, domains
- Access Rights: Model permissions by security group
- Record Rules: Domain-based access rules
- Controller Routes: HTTP/JSON routes with auth types
- Scheduled Actions: Cron jobs with intervals
- Report Templates: QWeb templates
- Module Metadata: Dependencies, version, description
Multiple References
Each element can have multiple file:line references:
- definition: Where it's originally defined
- inheritance: Where models are extended
- override: Where methods/fields are overridden
- reference: Where it's referenced
- modification: Where views are modified with xpath
Installation
Prerequisites
- Python 3.10+
- uv package manager
Setup
# Clone or navigate to the project
cd odoo-index-mcp
# Create .env file
cp .env.example .env
# Edit .env and set your ODOO_PATH
nano .env
# Install dependencies with uv
uv sync
Usage
CLI Tool
# Full indexing
uv run python cli.py --index
# Incremental indexing (skip unchanged files)
uv run python cli.py --index --incremental
# Index specific modules
uv run python cli.py --index --modules sale,account,stock
# Clear database and re-index
uv run python cli.py --clear --index
# Show statistics
uv run python cli.py --stats
# Search from CLI
uv run python cli.py --search "sale.order" --type model
uv run python cli.py --search "partner_id" --type field --module sale
# Search XML IDs
uv run python cli.py --search-xml-id "action_view_%"
uv run python cli.py --search-xml-id "action_view_sale_order" --module sale
MCP Server
# Start MCP server
uv run odoo-index-mcp
Claude Desktop Integration
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"odoo-index": {
"command": "uv",
"args": ["run", "odoo-index-mcp"],
"cwd": "/path/to/odoo-index-mcp",
"env": {
"ODOO_PATH": "/path/to/odoo"
}
}
}
}
MCP Tools
The server provides 7 MCP tools:
1. search_odoo_index
Search for elements by name with wildcard support.
Parameters:
query(str): Search term (supports SQL LIKE with %)item_type(str, optional): Filter by typemodule(str, optional): Filter by moduleparent_name(str, optional): Filter by parent (for fields/methods)limit(int, default=50): Max results
Example:
search_odoo_index(query="sale.order", item_type="model")
search_odoo_index(query="partner%", item_type="field", module="sale")
2. get_item_details
Get complete details for a specific element including related items.
Parameters:
item_type(str): Type of itemname(str): Item nameparent_name(str, optional): Parent (for fields/methods)module(str, optional): Module to disambiguate
Example:
get_item_details(item_type="model", name="sale.order")
get_item_details(item_type="field", name="partner_id", parent_name="sale.order")
3. list_modules
List all indexed modules with item counts.
Parameters:
pattern(str, optional): Filter by name pattern
Example:
list_modules()
list_modules(pattern="sale")
4. get_module_stats
Get detailed statistics for a module.
Parameters:
module(str): Module name
Example:
get_module_stats(module="sale")
5. find_references
Find all references to an element across the codebase.
Parameters:
item_type(str): Type of itemname(str): Item namereference_type(str, optional): Filter by type (definition/inheritance/etc)
Example:
find_references(item_type="model", name="sale.order")
find_references(item_type="model", name="sale.order", reference_type="inheritance")
6. search_by_attribute
Advanced search by element attributes.
Parameters:
item_type(str): Type to searchattribute_filters(dict): Attribute filtersmodule(str, optional): Filter by modulelimit(int, default=50): Max results
Example:
# Find all Many2one fields
search_by_attribute(
item_type="field",
attribute_filters={"field_type": "Many2one"}
)
# Find all transient models (wizards)
search_by_attribute(
item_type="model",
attribute_filters={"model_type": "transient"}
)
# Find all form views
search_by_attribute(
item_type="view",
attribute_filters={"view_type": "form"}
)
7. search_xml_id
Search for XML IDs by name pattern.
Parameters:
query(str): Search term (supports SQL LIKE patterns with %)module(str, optional): Filter by modulelimit(int, default=50): Max results
Example:
# Find all action_view XML IDs
search_xml_id(query="action_view_%")
# Find specific action
search_xml_id(query="action_view_sale_order")
# Find form views in sale module
search_xml_id(query="%_form_view", module="sale")
Performance
- Indexing Speed: ~500-1000 files/second with concurrent processing and async database operations
- Database Size: ~50-100MB for typical Odoo installation
- Search Speed: <50ms for exact match, <200ms for pattern search
- Memory Usage: <500MB during indexing, <100MB when serving
- Database: Async connection pooling with aiosqlite for efficient concurrent writes
Configuration
Environment variables in .env:
# Required
ODOO_PATH=/path/to/odoo
# Optional (with defaults)
SQLITE_DB_PATH=./odoo_index.db
LOG_LEVEL=INFO
MAX_CONCURRENT_MODULES=4
MAX_CONCURRENT_FILES=8
Project Structure
odoo-index-mcp/
├── pyproject.toml # uv project config
├── .env.example # Environment template
├── .python-version # Python version
├── README.md # This file
├── cli.py # CLI tool
├── odoo_index_mcp/
│ ├── __init__.py
│ ├── config.py # Configuration
│ ├── database.py # SQLite operations
│ ├── indexer.py # Main indexing logic
│ ├── server.py # FastMCP server
│ ├── tools.py # MCP tool implementations
│ └── parsers/
│ ├── __init__.py
│ ├── python_parser.py # AST parsing for Python
│ ├── xml_parser.py # XML parsing for views/data
│ ├── csv_parser.py # CSV parsing for access rights
│ └── manifest_parser.py # Manifest file parsing
Database Schema
The index uses a normalized SQLite schema with 3 main tables:
- indexed_items: Core item data (type, name, module, attributes JSON)
- item_references: File locations (many-to-one with items)
- file_metadata: File hashes for incremental indexing
All queries use proper indexes for fast lookups.
Development
# Install development dependencies
uv sync
# Run tests (TODO: add tests)
uv run pytest
# Format code
uv run black .
# Type checking
uv run mypy .
License
MIT
Contributing
Contributions welcome! Please:
- Fork the repo
- Create a feature branch
- Add tests for new functionality
- Submit a pull request
Support
For issues or questions:
- Open an issue on GitHub
- Check the documentation in ODOO_CODE_INDEXER.md
Roadmap
Future enhancements (not in v1):
- [ ] Call graph analysis
- [ ] Full-text search in method bodies
- [ ] Dependency graph visualization
- [ ] Watch mode (auto-reindex on changes)
- [ ] Web UI for browsing
- [ ] Export to other formats
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。