appwrite vs @cognigy/plugin-engine
appwrite is a plugin bundle for AI coding tools published by appwrite. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). @cognigy/plugin-engine is an MCP server published by Cognigy. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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
| Marketplace |  appwrite |  @cognigy/plugin-engine |
|---|---|---|
| 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 |
| npm registry (MCP servers) | Not listed | Listed Version: 1.22.6 Downloads/month (npm): 2 606 Downloads/week (npm): 1 162 Forks (GitHub): 14 Stars (GitHub): 18 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
| Fact | appwrite | @cognigy/plugin-engine |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 10 (worse) | 18 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 14 (better) |
| Last release (differs) | Not published | 2026-11-06 |
| Where it runs (differs) | Remote server (mcp.appwrite.io) | On your machine (@cognigy/plugin-engine) |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 15 | Not a bundle |
| Licence (differs) | BSD-3-Clause | MIT |
| Repository (differs) | github.com/appwrite/claude-plugin | github.com/cognigy/cognigy-plugin |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 401 | no 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
Appwrite tools for Claude Code, including SDK skills, Appwrite MCP servers, and deployment commands.
@cognigy/plugin-engine
MCP server engine for the NiCE Cognigy Plugin (Claude Code, Codex, and more)
How to run each
appwrite As a Claude Code plugin
/plugin install appwrite@claude-plugins-official@cognigy/plugin-engine
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only appwrite 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
The marketplaces of @cognigy/plugin-engine publish no settings it asks for, so we do not compare settings.
What it can do: appwrite · What it can do: @cognigy/plugin-engine · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.