Ext Ops Panel
Open dashboard
Comparison

@chykalophia/clickup-mcp-server vs Jitbit MCP Server and API by Cotlet

@chykalophia/clickup-mcp-server is an MCP server published by Chykalophia. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Jitbit MCP Server and API by Cotlet is an MCP server published by cotlet.dev. 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
Marketplace@chykalophia/clickup-mcp-serverJitbit MCP Server and API by Cotlet
npm registry (MCP servers) Listed
Version: 6.2.0
Downloads/month (npm): 663
Downloads/week (npm): 255
Forks (GitHub): 16
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
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

@chykalophia/clickup-mcp-server vs Jitbit MCP Server and API by Cotlet
Fact@chykalophia/clickup-mcp-serverJitbit MCP Server and API by Cotlet
Marketplaces that list it11
Stars (GitHub) (differs)8No figure on GitHub
Forks (GitHub) (differs)16No figure on GitHub
Last release (differs)Not published2026-11-09
Where it runs (differs)On your machine (@chykalophia/clickup-mcp-server)Remote server (cotlet.dev/mcp/v1/jitbit/connect)
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/chykalophia/clickup-mcp-server---enhancedNot stated
Changes in the last 7 days (differs)05
First seen (differs)2026-10-122026-11-09
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

@chykalophia/clickup-mcp-server

In its own words, on npm registry (MCP servers):

An intelligent Model Context Protocol server for ClickUp API integration with 157 tools, AI-powered efficiency optimization, smart tool suggestions, and context-aware workflow recommendations

Jitbit MCP Server and API by Cotlet

In its own words, on Official MCP Registry:

Jitbit MCP server: assign ticket, update ticket, close ticket, merge tickets, create ticket.

How to run each

@chykalophia/clickup-mcp-server

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

Jitbit MCP Server and API by Cotlet As a remote MCP server

Claude Code
claude mcp add --transport http jitbit https://cotlet.dev/mcp/v1/jitbit/connect

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

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

What it can do: @chykalophia/clickup-mcp-server · What it can do: Jitbit MCP Server and API by Cotlet · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.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