MCP (Model Context Protocol)

This server also exposes an MCP endpoint, giving an LLM client the same module search, dependency-graph, code-analysis and maintenance data shown in this dashboard. It's split into small, single-purpose tools instead of one big "give me everything" call, so a client only fetches the detail it actually needs for a given question - look up a module's contents, its dependencies and its code are three separate tools rather than one reply carrying all three every time.

MCP endpoint URL
https://mcp.ommd.info/mcp

Available tools

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 module) - the entry point when you don't know which repository carries them.
  • search_repositories
    Find a GitHub/GitLab repository by name - e.g. locate OCA's per-country/topic repos such as l10n-spain or account-invoicing.
  • list_repository_modules
    List 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
    See 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 for the module, when its repository documents them.
  • get_module_dependencies
    The full dependency closure for one module: every Odoo module, Python package and system binary it needs, directly or transitively.
  • get_module_code_analysis
    The XML views and Odoo models/fields/methods the module defines or extends. The most detailed - and heaviest - tool on this server.

Maintainers

  • 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.

Installation & usage

Pick your client below and copy its configuration snippet to point it at the endpoint URL above.

Command line

claude mcp add --transport http oghcollector https://mcp.ommd.info/mcp

Or via .mcp.json (project-scoped, 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 below must be reachable over the public internet (a localhost URL will not work here; use the local bridge tab instead for local development).

  1. Pro / Max plan: go to Settings → Customize → Connectors, click +, choose Add custom connector.
  2. Team / Enterprise plan: an owner goes to Organization settings → Connectors, clicks Add → Custom → Web; members then enable it from Settings → Customize → Connectors.
  3. Paste the endpoint URL:
https://mcp.ommd.info/mcp

Click Add, then enable the connector for a conversation from the + menu in the chat composer.

.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 here. Fully quit and reopen Cursor afterwards — MCP servers are only loaded at startup.

.vscode/mcp.json (workspace) or the user profile mcp.json 

{
  "servers": {
    "oghcollector": {
      "type": "http",
      "url": "https://mcp.ommd.info/mcp"
    }
  }
}

Open the Command Palette → MCP: Add Server… to have VS Code write this for you, or edit the file directly. VS Code runs locally too, so localhost works fine.

Any client that only supports launching a local stdio server (no native remote/HTTP option) can still reach this endpoint through mcp-remote, a small bridge run with npx. Since it runs as a local process on your own machine, this also works when the endpoint is on localhost — use it 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 the --allow-http flag to the args array.