Appwrite MCP

Appwrite's MCP server puts the backend-as-a-service platform's management API behind Model Context Protocol tools, so an assistant can operate an Appwrite project instead of only writing code against it. It covers the core product surface: databases, collections, documents and attributes; authentication users and sessions; teams and memberships; storage buckets and files; serverless functions with their deployments and executions; and project-level settings. Access is granted with a project ID and an API key, and the key's scopes decide which parts of the project the agent may touch. The typical loop is scaffolding and inspection. An agent can create a collection with typed attributes and indexes, seed documents into it, list users to debug a login problem, check function execution logs after a deploy, or generate client code that matches the schema it just created. The server can be pointed at Appwrite Cloud or at a self-hosted instance, which matters for teams that keep their data on their own infrastructure. It suits solo developers and small product teams who use Appwrite as their backend and want an agent to handle the repetitive setup work: defining schemas, wiring permissions and querying project state while debugging. Because it is open source and self-hostable, the exposed toolset can be trimmed to a subset before handing an agent a key with write scopes.