Appwrite MCP (official)

70/100

Capped at 70: no passing tool call yet; the tests add up to 75. Why scores are capped

Last tested 2026-10-31 (Fresh: tested within 30 days) Needs key API key

No advisories in range for tested 2.2.3 (checked 2026-11-09)

Security review: not tested

Test points add up to 75; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (75/100)

  • Install20/20
  • Handshake5/30
  • Maintenance25/25
  • Docs15/15
  • License10/10

Transport (tested 2026-10-31): stdio

Tested version: 2.2.3 · tested 2026-10-31

Token cost (estimate): the figure is pending. We have no tools/list capture to estimate from.

Permissions: tool permissions pending · Auth: API key · Rate limit: unknown · Pricing unit: unknown

Auth: API key. Rate limit: unknown. Pricing unit: unknown.

recorded env/README key names: APPWRITE_API_KEY

Score 70/100 · Tools 0 · Token cost pending · Compare · Last tested 2026-10-31 · Version tested 2.2.3 · Package mcp-server-appwrite · Repo appwrite/mcp

Summary: Appwrite MCP (official) requires credentials or a backing service before it will list tools.

Evidence summary

Handshake
auth-gated
Tools listed
0
Context cost
Pending The token cost figure is pending. ranking
API key
Needs a key
Tested
2026-10-31

Test results

TestResultPointsEvidence
installpass20uv pip install mcp-server-appwrite (Python venv, Linux) succeeded in 1s.
handshakeauth-gated5Auth-gated: without credentials the server only printed a missing-credential message and did not list tools ("… [appwrite-mcp] ERROR: APPWRITE_PROJECT_ID and APPWRITE_API_KEY must be set in environment variables exited code 1; …"). Not tested with real credentials; not counted as working.
maintenancepass25Repo pushed 0 days before test; 72 GitHub stars.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)).
licensepass10MIT (OSI-approved).

Local-model readiness

Not tested

Not yet tested (no tools/list response without credentials).

What we tested and what we didn't

Tested on 2026-10-31

  • Install from the registry
  • We attempted an MCP initialize with no credentials; it stopped at a credential check, so we never reached the tool list (Method details: initialize did not complete; tools/list not sent)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Checked on 2026-11-09 for version 2.2.3 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.

No published advisories found in OSV and GitHub advisories for mcp-server-appwrite 2.2.3 as of 2026-11-09. This is not a security audit.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.

Raw test record (JSON)
{
  "name": "mcp-server-appwrite",
  "version": "2.2.3",
  "registry": "pypi",
  "status": "auth-gated",
  "tested": "2026-10-31",
  "tools_count": null,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`uv pip install mcp-server-appwrite` (Python venv, Linux) succeeded in 1s."
    ],
    "handshake": [
      "auth-gated",
      5,
      "Auth-gated: without credentials the server only printed a missing-credential message and did not list tools (\"\u2026 [appwrite-mcp] ERROR: APPWRITE_PROJECT_ID and APPWRITE_API_KEY must be set in environment variables exited code 1; \u2026\"). Not tested with real credentials; not counted as working."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 72 GitHub stars."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  }
}

Install

uvx mcp-server-appwrite

Pin the version we tested

uvx mcp-server-appwrite==2.2.3

pip install mcp-server-appwrite==2.2.3

tested 2026-10-31. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "appwrite-mcp": {
      "command": "uvx",
      "args": [
        "mcp-server-appwrite==2.2.3"
      ],
      "env": {
        "APPWRITE_API_KEY": "<your key>"
      }
    }
  }
}

Tools listed

Not available (handshake did not complete without credentials).

Quick config

{
  "mcpServers": {
    "appwrite-mcp": {
      "command": "uvx",
      "args": [
        "mcp-server-appwrite"
      ],
      "env": {
        "APPWRITE_API_KEY": "<your key>"
      }
    }
  }
}

API key: set APPWRITE_API_KEY in env (replace <your key>). Our handshake ran without it; real use needs it.

Add to config Opens the config generator with this server selected.

Setup

Without credentials it said (verbatim): … [appwrite-mcp] ERROR: APPWRITE_PROJECT_ID and APPWRITE_API_KEY must be set in environment variables exited code 1; …

Env var seen in our test: APPWRITE_API_KEY

  1. Install. Run uv pip install mcp-server-appwrite (Python venv). This is the exact command we ran on 2026-10-31.
  2. Configure. Add the mcpServers entry below to your MCP client config and set APPWRITE_API_KEY.
  3. Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
  "mcpServers": {
    "appwrite-mcp": {
      "command": "uvx",
      "args": [
        "mcp-server-appwrite"
      ],
      "env": {
        "APPWRITE_API_KEY": "<your key>"
      }
    }
  }
}

Not tested with credentials We have not tested this with real credentials.

Test history

Follow this server (RSS) · Monthly changelog

Related: Best dev MCP servers · Troubleshooting: Missing environment variable · MCP servers that need an API key · How to protect AI API keys

FAQ

Is Appwrite MCP deprecated?

No. mcp-server-appwrite was not deprecated or archived when we last tested it on 2026-10-31.

What replaces Appwrite MCP?

Nothing; Appwrite MCP (official) is not deprecated as of 2026-10-31.

Does Appwrite MCP need an API key?

Yes. Without credentials it only printed a missing-credential message and did not list tools (auth-gated).

Embed the badge

TestedMCP: 70/100, tested 2026-10-31

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue