MCP server
Give an LLM client the module search, dependency-graph, code-analysis and maintenance data of this site through the Model Context Protocol. Read-only, no API key of its own (behind a proxy with auth? see below).
https://mcp.ommd.info/mcp
Connect your client
Every snippet points at the endpoint above.
Run once in a terminal:
claude mcp add --transport http oghcollector https://mcp.ommd.info/mcp
Or share it with the whole project in a .mcp.json checked into git:
{
"mcpServers": {
"oghcollector": {
"type": "http",
"url": "https://mcp.ommd.info/mcp"
}
}
}
Claude Desktop and claude.ai connect to custom connectors from Anthropic's cloud, not from your own
machine: the URL must be reachable over the public internet. A localhost URL won't work
here — for local development use the
local bridge
instead.
- Pro / Max plan: go to Settings → Customize → Connectors, click + and choose Add custom connector.
- Team / Enterprise plan: an owner goes to Organization settings → Connectors, clicks Add → Custom → Web; members then enable it from Settings → Customize → Connectors.
- Paste the endpoint URL and click Add:
https://mcp.ommd.info/mcp
Then enable the connector for a conversation from the + menu in the chat composer.
Add it to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"oghcollector": {
"url": "https://mcp.ommd.info/mcp"
}
}
}
Cursor runs locally, so a localhost URL works fine. Fully quit and reopen Cursor
afterwards — MCP servers are only loaded at startup.
Add it to .vscode/mcp.json (workspace) or the user profile mcp.json:
{
"servers": {
"oghcollector": {
"type": "http",
"url": "https://mcp.ommd.info/mcp"
}
}
}
Or open the Command Palette → MCP: Add Server… and let VS Code write it for you.
VS Code runs locally too, so localhost works fine.
Clients that can only launch a local stdio server reach the endpoint through
mcp-remote,
a small bridge run with npx. It runs on your own machine, so it also works with a
localhost endpoint — handy for local development with clients whose connector UI
requires a public URL.
{
"mcpServers": {
"oghcollector": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.ommd.info/mcp"]
}
}
}
Requires Node.js 18+. If the URL uses plain http:// on a host other than
localhost, add --allow-http to the args array.
Behind authentication
If this endpoint sits behind a reverse proxy with HTTP Basic auth (e.g. Traefik basicAuth), send an Authorization header.
Build the header value once and keep it in an environment variable, not in files you commit:
export OGH_MCP_AUTH="Basic $(printf '%s' 'user:password' | base64)"
Claude Code
claude mcp add --transport http oghcollector https://mcp.ommd.info/mcp \
--header "Authorization: $OGH_MCP_AUTH"
Or in .mcp.json; ${OGH_MCP_AUTH} is expanded from each user's environment, so the secret stays out of git:
{
"mcpServers": {
"oghcollector": {
"type": "http",
"url": "https://mcp.ommd.info/mcp",
"headers": { "Authorization": "${OGH_MCP_AUTH}" }
}
}
}
Cursor — mcp.json:
{
"mcpServers": {
"oghcollector": {
"url": "https://mcp.ommd.info/mcp",
"headers": { "Authorization": "${env:OGH_MCP_AUTH}" }
}
}
}
VS Code — mcp.json; VS Code asks for the value once and stores it:
{
"inputs": [
{ "type": "promptString", "id": "ogh-auth", "description": "Authorization header (Basic ...)", "password": true }
],
"servers": {
"oghcollector": {
"type": "http",
"url": "https://mcp.ommd.info/mcp",
"headers": { "Authorization": "${input:ogh-auth}" }
}
}
}
Other clients / local — pass the header to mcp-remote. The value goes through env so the space in Basic … doesn't break the argument list:
{
"mcpServers": {
"oghcollector": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.ommd.info/mcp", "--header", "Authorization:${OGH_MCP_AUTH}"],
"env": { "OGH_MCP_AUTH": "Basic dXNlcjpwYXNzd29yZA==" }
}
}
}
Claude Desktop / claude.ai custom connectors can't send a Basic auth header (they support no auth or OAuth only).
Use the mcp-remote config above with Claude Desktop, or exempt the /mcp route from
the proxy's auth and restrict it another way (IP allowlist).
Available tools
Small single-purpose tools: a client fetches only the detail a question needs.
Find modules & repositories
- search_modules
- Find modules by (part of) their technical name, optionally filtered by Odoo version or whether they're installable.
- list_modules_by_criteria
- Discover modules across every repository by category, a free-text term and/or reverse dependency (which modules depend on a given one) — the entry point when you don't know which repository carries them.
- semantic_search_modules
- Describe the functionality you need in plain words, any language, and get the closest modules by meaning — “send invoices to the tax agency” finds e-invoicing modules even when no keyword overlaps.
- search_repositories
- Find a GitHub/GitLab repository by name, e.g. OCA's per-country/topic repos such as
l10n-spainoraccount-invoicing. - list_repository_modules
- Every module in a repository at once, with maintenance signals (last commit, committers) and direct dependencies — the go-to tool for assembling a module pack.
- list_module_versions
- Every recorded version of a module, with first/last-seen dates and which one is the latest.
One module in detail
- get_module
- Manifest metadata for one module: description, authors/maintainers, license, category and install flags.
- get_module_docs
- Rendered install/usage instructions, when its repository documents them.
- get_module_dependencies
- The full dependency closure: every Odoo module, Python package and system binary it needs, directly or transitively — plus a license review of it.
- compare_module_versions
- What changed between two Odoo versions: manifest, dependencies, models/fields/methods, views and HTTP routes — for planning a migration.
- get_module_code_analysis
- The XML views, models/fields/methods, records and controllers the module defines or extends. The most detailed — and heaviest — tool on this server.
Packs & maintainers
- review_module_licenses
- License review of a set of modules deployed together, dependencies included: the license of the combined work, proprietary modules pulled in and conflicts. Not legal advice.
- get_committer_activity
- What else a specific person has committed to, e.g. to check whether a module's top contributor is still active elsewhere before relying on it.
Doodba projects
- list_doodba_projects
- The Doodba projects collected, optionally of an organization, an Odoo version or using a module: template drift, patches and how many of their PRs are merged or closed, pip advisories, credentials in their files.
- get_doodba_project
- One project whole: pending template commits, repos.yaml patches with their upstream state, addons and whether each exists in the next Odoo version, lint hooks, dependencies and advisories. Both off unless the MCP server sets
OGHCOLLECTOR_PROJECTS_ENABLED.
Live instance
- scan_instance
- Anonymous probe of a running Odoo instance by URL: version, modules, TLS certificate, debug mode, cookie flags and an exposed database manager. Off unless the MCP server sets
OGHCOLLECTOR_SCAN_ENABLED.