Ext Ops Panel
Open dashboard
Comparison

appwrite vs Clize

appwrite is a plugin bundle for AI coding tools published by appwrite. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). Clize is an MCP server published by clize.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceappwriteClize
Claude Code: claude-plugins-official Listed
Version: 0.2.0
Forks (GitHub): 1
Stars (GitHub): 10
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 10
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.52.0
Downloads/month (npm): 5 560
Downloads/week (npm): 493
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

appwrite vs Clize
FactappwriteClize
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)10 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)Remote server (mcp.appwrite.io)On your machine (@clize/clize)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Parts of the bundle (differs)15Not a bundle
Licence (differs)BSD-3-ClauseNot stated
Repository (differs)github.com/appwrite/claude-plugingithub.com/cooldk/clize-cli
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

appwrite

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

Appwrite tools for Claude Code, including SDK skills, Appwrite MCP servers, and deployment commands.

Clize

In its own words, on Official MCP Registry:

Real-world actions for AI coding agents: an inbox with approval outbox, deploys, domains, payments.

How to run each

appwrite As a Claude Code plugin

Claude Code
/plugin install appwrite@claude-plugins-official

Clize As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio clize -- npx -y --package @clize/clize clize-mcp @clize/clize

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 Clize publish no settings it asks for, so we do not compare settings.

What it can do: appwrite · What it can do: Clize · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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