Can AI agents automate Appwrite?

Appwrite Cloud and self-hosted Appwrite backends are automatable today through a first-party MCP server, a public REST and GraphQL API, and the official Appwrite CLI. This record is Appwrite, not Firebase, Supabase, or PocketBase. Cloud MCP is a hosted HTTP server at https://mcp.appwrite.io/ that authenticates with browser OAuth and does not use API keys. It exposes four compact tools — appwrite_get_context, appwrite_search_tools, appwrite_call_tool, and appwrite_search_docs — that search an internal catalog of 38 services and 981 methods. Self-hosted instances cannot use that hosted endpoint. They run mcp-server-appwrite locally over stdio with a project API key, covering 26 services and 647 methods. Those are two transports, not one. The REST API authenticates with API keys (X-Appwrite-Key), JWTs (X-Appwrite-JWT), or account session cookies. GraphQL at /v1/graphql covers every REST endpoint except OAuth. Realtime is a separate WebSocket subscription API; vendor docs state Server SDKs and API keys do not currently access it. Official client and server SDKs cover JavaScript, Python, Dart, PHP, Ruby, .NET, Go, Swift, Kotlin, and Rust. The CLI installs on macOS, Windows, and Linux, has a command for every Server API endpoint, supports --json, and runs non-interactively with an API key for CI. Appwrite Functions are the documented scripting surface. Webhooks POST on resource events. Cloud publishes Free, Pro (from $25/month), and Enterprise plans; Free projects pause after one week of inactivity. Connector catalogs were not opened. Computer-use viability is unassessed. API, MCP, and CLI each score 8. MCP is the best path because it is the vendor agent interface, with hosted OAuth HTTP for Cloud and a separate stdio plus API-key path for self-hosted.

Best path today: mcp · Overall automatability: 8/10