MCP100 verdict
Not currently recommended. Shortlist — editorially admitted, not a Recommended endorsement.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Exact tool inventory/scope varies; hosted OAuth recommended
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Evidence scope
73 MCP repository stars
132,125 package downloads / 30 days · Third-party: PyPI Stats
Repository identity: appwrite/mcp
Package identity: mcp-server-appwrite · version 1.0.21
Stars observed October 20, 2026 · Downloads observed October 20, 2026
Exact current first-party MCP repository; stars are MCP-specific repository evidence.
Exact MCP-specific PyPI package. Download count is the disclosed PyPI Stats `last_month` signal.
Publisher activity observed October 19, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-19
Type-appropriate, source-backed setup for this mcp server profile.
{"url":"https://mcp.appwrite.io/mcp"}Capability
Appwrite MCP is a Appwrite MCP integration for appwrite project, database, authentication and storage administration. Use for Appwrite backend development and administration. Administrative APIs touch users, application data and secrets.
Search Appwrite documentation
Cloud vs self-hosted may expose different tool catalogs
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
https://mcp.appwrite.io/mcp
Reviewed access
Reviewed sources
Related reviewed MCPs
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens.
Choose this instead if
Choose Codebase Memory MCP instead if repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages.
Recommended after reviewed 2026-09-25 admission dossier: all_current_selected_gates_pass.
Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Choose this instead if
Choose Terraform MCP instead if connect compatible AI clients to HashiCorp's documented MCP capabilities.
Recommended after reviewed Batch 1 correction: exact 61-tool contract closes the prior formal Recommended gap.
Connect agents to Azure resources and more than forty Azure services.
Choose this instead if
Choose Azure MCP Server instead if discovering and inspecting resources across supported Azure services.
Connect agents to Azure resources and more than forty Azure services.
Appwrite is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
A Model Context Protocol server for Appwrite. It exposes Appwrite's API — databases, users, functions, teams, storage, and more — as tools your MCP client can call.
Connect to the hosted server at https://mcp.appwrite.io/ and authenticate
through your browser. The first time you connect, your client opens an Appwrite
consent screen; approve the scopes and you're connected. There are no keys to
copy. The conventional https://mcp.appwrite.io/mcp URL is also supported and
connects to the same server.
Pick your client below. Each adds the hosted Appwrite Cloud server.
claude mcp add --transport http appwrite https://mcp.appwrite.io/
Then, inside a Claude Code session, run /mcp, select appwrite, and follow
the browser prompt to authenticate.
Go to Settings → Connectors → Add custom connector and paste
https://mcp.appwrite.io/. Available on Pro and Max plans; on Team and
Enterprise plans only an organization Owner can add custom connectors.
If you don't see that option (free plan, or a Team/Enterprise member), bridge the remote server through stdio instead (requires Node.js). Go to Settings → Developer → Local MCP servers, click Edit Config, and add:
{
"mcpServers": {
"appwrite": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]
}
}
}
Restart Claude Desktop; the server appears under Local MCP servers and a browser window opens to authenticate.
Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
{
"mcpServers": {
"appwrite": {
"url": "https://mcp.appwrite.io/"
}
}
}
Cursor prompts you to log in through the browser; the server then shows up under Settings → MCP with its tools enabled.
Edit .vscode/mcp.json (workspace) or your user configuration via the Command
Palette → MCP: Open User Configuration.
{
"servers": {
"appwrite": {
"type": "http",
"url": "https://mcp.appwrite.io/"
}
}
}
Edit ~/.codex/config.toml.
[mcp_servers.appwrite]
url = "https://mcp.appwrite.io/"
Then authenticate from the terminal:
codex mcp login appwrite
In the Codex GUI, you can instead add the server from the MCP settings —
set the URL to https://mcp.appwrite.io/ and leave the token and header
fields empty (authentication happens through the browser):
Edit opencode.json (project) or ~/.config/opencode/opencode.json (global).
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"appwrite": {
"type": "remote",
"url": "https://mcp.appwrite.io/",
"enabled": true
}
}
}
Edit ~/.codeium/windsurf/mcp_config.json.
{
"mcpServers": {
"appwrite": {
"serverUrl": "https://mcp.appwrite.io/"
}
}
}
gemini mcp add --transport http appwrite https://mcp.appwrite.io/
Or edit ~/.gemini/settings.json (note the key is httpUrl, not url):
{
"mcpServers": {
"appwrite": {
"httpUrl": "https://mcp.appwrite.io/"
}
}
}
Gemini CLI opens the browser OAuth flow automatically on first connect. To
re-authenticate, run /mcp auth appwrite inside a session.
Edit ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (project workspace).
{
"mcpServers": {
"appwrite": {
"serverUrl": "https://mcp.appwrite.io/"
}
}
}
⚠️ Note: Antigravity strictly requires the
serverUrlkey for remote transport. Using legacy fields likeurlorhttpUrlwill cause tool registration to fail silently.
Antigravity opens the browser OAuth flow automatically on first connect. If you manually edit the JSON file, navigate to Settings → Customizations → Installed MCP Servers and click Refresh to reload the tool definitions.
copilot mcp add --transport http appwrite https://mcp.appwrite.io/
Or run /mcp add inside a session, or edit ~/.copilot/mcp-config.json:
{
"mcpServers": {
"appwrite": {
"type": "http",
"url": "https://mcp.appwrite.io/"
}
}
}
A browser window opens to authenticate on first connect. Check status with
/mcp.
Go to Settings → AI → MCP Servers → Add Server → Add Remote Server, or add
to your settings.json (zed: open settings):
{
"context_servers": {
"appwrite": {
"url": "https://mcp.appwrite.io/"
}
}
}
Zed prompts you to authenticate through the browser on first connect.
Go to Settings → Agents → MCP servers → + Add, choose the URL-based
server type, and enter https://mcp.appwrite.io/.
Warp opens a browser window to authenticate on first connect.
JetBrains IDEs don't yet support OAuth for remote MCP servers, so bridge through stdio (requires Node.js). Go to Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add, switch to the JSON view, and paste:
{
"mcpServers": {
"appwrite": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]
}
}
}
A browser window opens to authenticate on first connect.
Cline doesn't yet support OAuth for remote MCP servers, so bridge through stdio (requires Node.js). In the Cline panel, open the MCP Servers icon → Configure tab → Configure MCP Servers, and add:
{
"mcpServers": {
"appwrite": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]
}
}
}
A browser window opens to authenticate on first connect.
Running your own Appwrite instance? Run the MCP server locally over stdio and
authenticate with a project API key. See docs/self-hosted.md
for per-client setup.
appwrite_search_docs tool and how to rebuild its index.This MCP server is licensed under the MIT License. See the LICENSE file for details.