Ext Ops Panel
Open dashboard
Comparison

activecollab-mcp vs Docketwise MCP by usefulapi

activecollab-mcp is an MCP server published by devjtv. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Docketwise MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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-mcpDocketwise MCP by usefulapi
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: 1.1.5
Forks (GitHub): 0
Stars (GitHub): 1
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 Docketwise MCP by usefulapi
Factactivecollab-mcpDocketwise MCP by usefulapi
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-11-04 (worse)2026-11-07 (better)
Where it runs (differs)On your machine (activecollab-mcp)Remote server (docketwise.usefulapi.io/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/devjtv/active-collab-mcpgithub.com/m190/usefulapi-mcp
Changes in the last 7 days (differs)15
First seen (differs)2026-10-122026-11-06
Endpoint at the last check (differs)no remote endpoint we checkResponded less than an hour ago, requires authentication

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.

Docketwise MCP by usefulapi

In its own words, on Official MCP Registry:

Read contacts, matters, invoices and documents; create contacts, matters and notes in Docketwise.

How to run each

activecollab-mcp

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

Docketwise MCP by usefulapi As a remote MCP server

Claude Code
claude mcp add --transport http docketwise https://docketwise.usefulapi.io/mcp

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

Only Docketwise MCP by usefulapi has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: activecollab-mcp · What it can do: Docketwise MCP by usefulapi · 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