Ext Ops Panel
Open dashboard
Comparison

casemgr-channel vs IntakeQ MCP by usefulapi

casemgr-channel is a plugin bundle for AI coding tools published by mstang. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). IntakeQ 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-10-22. 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
Marketplacecasemgr-channelIntakeQ MCP by usefulapi
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.16.4
Forks (GitHub): 0
Stars (GitHub): 0
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

casemgr-channel vs IntakeQ MCP by usefulapi
Factcasemgr-channelIntakeQ MCP by usefulapi
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-22
Where it runs (differs)Installs as a plugin bundleRemote server (intakeq.usefulapi.io/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/mstang/casemgr-channelgithub.com/m190/usefulapi-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago, requires a key

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

casemgr-channel

In its own words, on Claude Code: claude-plugins-community:

Pushes AI work items from CaseMgr — a shared workspace for you and your AI agent — into your running Claude Code session as channel events. When a CMMN workflow in CaseMgr produces a pending work item, the plugin forwards it via SSE so Claude can claim, execute, and complete it without any human prompt. Uses Bearer-token auth, real-time event delivery with polling fallback, and a /casemgr-channel:configure skill for setup. Claude handles the actual work via the existing casemgr MCP tools (cases, notes, tasks, semantic search, file management, billing, and 178 more).

IntakeQ MCP by usefulapi

In its own words, on Official MCP Registry:

Search clients, appointments, intakes, notes and invoices in IntakeQ, and book or cancel visits.

How to run each

casemgr-channel As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install casemgr-channel@claude-community

IntakeQ MCP by usefulapi As a remote MCP server

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

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

Only IntakeQ 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: casemgr-channel · What it can do: IntakeQ MCP by usefulapi · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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