Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Appwrite MCPCodebase Memory MCP

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedPlaywright MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Appwrite MCPShortlist candidate	Codebase Memory MCPMCP100 Recommended
Task fit
Best for	Appwrite project, database, authentication and storage administration Use for Appwrite backend development and administration.	Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages
Not ideal for	Administrative APIs touch users, application data and secrets.	Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers
Avoid when	Administrative APIs touch users, application data and secrets.	The source tree cannot be indexed locally or persistent cache files are prohibited
Provenance
Provenance details	First-party MCP Appwrite · Publisher source ↗	First-party MCP DeusData · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Aug 14, 2026 Package: Aug 14, 2026
Popularity evidence
GitHub stars	73 GitHub stars · checked 2026-10-20	44,904 GitHub stars · checked 2026-09-25T18:35:00Z
Package downloads / 30 days	132,125 package downloads / 30 days · checked 2026-10-20	28,000 package downloads / 30 days · checked 2026-08-14T00:00:00.000Z
External adoption evidence	Not documented	npm: package downloads: 28,015Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Not documented	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Browser-based OAuth/consent flow; the user approves scopes and no API key needs to be copied into the MCP client.	local stdio; no remote auth needed
Cost	Appwrite's reviewed MCP material says availability is tied to Pro/Max plans, while the broader Appwrite service has paid resource usage and overage pricing.	none beyond local resources
Permissions	The Appwrite MCP operates within the approved scopes/account. Appwrite notes that adding custom connectors on Team and Enterprise plans requires an organization Owner.	reads indexed source/project data; installer writes supported agent/editor configs/hooks
Data handling	Not documented in the reviewed sources. The reviewed Appwrite MCP README does not provide a clear MCP-specific retention/training statement.	local processing; current docs state no source/index/query/env/telemetry upload
Limitations
Tradeoffs	Exact tool inventory/scope varies; hosted OAuth recommended	Persistent indexing can reduce repeated reads, but consumes local storage and graph results can become stale until the repository is re-indexed. Version 0.10.8 includes correctness and reliability fixes affecting graph/search results and Windows behavior.
Risk context	Appwrite administrative/project APIs can touch users, application data, services and configuration. The consequence of a tool call depends on the OAuth scopes granted.	latest 0.10.x supported; SLSA/Sigstore/checksums/VirusTotal/security policy
Evidence date
Editorial review	2026-10-19	2026-09-23
Candidate evidence	2026-10-19	2026-09-25T18:35:00Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →