Appwrite offers a Model Context Protocol (MCP) server that allows LLMs to directly interact with Appwrite's API. Using the MCP server, you can use applications such as Claude Desktop, Cursor, Windsurf Editor, etc. to interact with your Appwrite project.
Getting started
Before launching the MCP server, you must set up an Appwrite project and create an API key with the necessary scopes enabled.
Integrate with popular AI tools
Install uv on your system with:
curl -LsSf https://astral.sh/uv/install.sh | sh
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
You can now integrate the MCP server with various popular AI-enabled code editors and LLM apps.
Want to integrate your AI tool?
If you are building an AI code-generation tool that can integrate with MCP servers and would like to collaborate, join our Technology Partners program.
Command-line arguments
Database tools are enabled by default. In addition you can pass arguments to uvx mcp-server-appwrite [args] to enable other MCP tools for various Appwrite APIs.
| Argument | Description |
--databases | Enables the Databases API |
--users | Enables the Users API |
--teams | Enables the Teams API |
--storage | Enables the Storage API |
--functions | Enables the Functions API |
--messaging | Enables the Messaging API |
--locale | Enables the Locale API |
--avatars | Enables the Avatars API |
--all | Enables all Appwrite APIs |
Enable only necessary MCP tools
When an MCP tool is enabled, the tool's definition is passed to the LLM, using up tokens from the model's available context window. As a result, the effective context window is reduced.
The default Appwrite MCP server ships with only the Databases tools (our most commonly used API) enabled to stay within these limits. Additional tools can be enabled using the flags below.