Ext Ops Panel
Open dashboard
Comparison

activecollab-mcp vs Detailing Manager

activecollab-mcp is an MCP server published by devjtv. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Detailing Manager is an MCP server published by RadoslavMoshev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceactivecollab-mcpDetailing Manager
PyPI (MCP servers) Listed
Version: 1.24.0
Downloads/month (PyPI): 773
Downloads/week (PyPI): 1 449
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.4
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

activecollab-mcp vs Detailing Manager
Factactivecollab-mcpDetailing Manager
Marketplaces that list it11
Last release (differs)2026-11-04Not published
Where it runs (differs)On your machine (activecollab-mcp)On your machine (@detailingmanager/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/devjtv/active-collab-mcpgithub.com/radoslavmoshev/detailingmanager
Changes in the last 7 days (differs)12
First seen (differs)2026-10-122026-11-06

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

activecollab-mcp

In its own words, on PyPI (MCP servers):

MCP server for ActiveCollab — exposes projects, tasks, comments, attachments, and time tracking to MCP-compatible LLM clients.

Detailing Manager

In its own words, on Official MCP Registry:

Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.

How to run each

activecollab-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Detailing Manager As a local MCP server: npm package

Claude Code
claude mcp add --env "DETAILING_MCP_API_KEY=<YOUR_DETAILING_MCP_API_KEY>" --transport stdio detailing-manager -- npx -y @detailingmanager/mcp

Requires: DETAILING_MCP_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of activecollab-mcp publish no settings it asks for, so we do not compare settings.

What it can do: activecollab-mcp · What it can do: Detailing Manager · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built