Appwrite MCP Server provides a Model Context Protocol server for interacting with Appwrite's API, allowing you to manage databases, users, functions, teams, and other resources within your Appwrite project through LLM interfaces.
Before using the MCP server, you need to set up an Appwrite project and create an API key with the necessary permissions. Create a .env
file in your working directory with the following:
APPWRITE_PROJECT_ID=your-project-id
APPWRITE_API_KEY=your-api-key
APPWRITE_ENDPOINT=https://cloud.appwrite.io/v1
Load these environment variables in your terminal:
source .env
for /f "tokens=1,2 delims==" %A in (.env) do set %A=%B
Get-Content .\.env | ForEach-Object {
if ($_ -match '^(.*?)=(.*)$') {
[System.Environment]::SetEnvironmentVariable($matches[1], $matches[2], "Process")
}
}
The simplest way to use the server is with uv
:
uvx mcp-server-appwrite [args]
Alternatively, install via pip:
pip install mcp-server-appwrite
Then run the server:
python -m mcp_server_appwrite [args]
Enable specific Appwrite API tools with these arguments:
--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
Note: Only the Databases API is enabled by default to conserve the model's context window. Each additional API tool you enable will use more of the available context.
claude_desktop_config.json
:{
"mcpServers": {
"appwrite": {
"command": "uvx",
"args": [
"mcp-server-appwrite"
],
"env": {
"APPWRITE_PROJECT_ID": "your-project-id",
"APPWRITE_API_KEY": "your-api-key",
"APPWRITE_ENDPOINT": "https://cloud.appwrite.io/v1"
}
}
}
}
MacOS:
env APPWRITE_API_KEY=your-api-key env APPWRITE_PROJECT_ID=your-project-id uvx mcp-server-appwrite
Windows:
cmd /c SET APPWRITE_PROJECT_ID=your-project-id && SET APPWRITE_API_KEY=your-api-key && uvx mcp-server-appwrite
mcp_config.json
to include:{
"mcpServers": {
"appwrite": {
"command": "uvx",
"args": [
"mcp-server-appwrite"
],
"env": {
"APPWRITE_PROJECT_ID": "your-project-id",
"APPWRITE_API_KEY": "your-api-key",
"APPWRITE_ENDPOINT": "https://cloud.appwrite.io/v1"
}
}
}
}
You can use the MCP inspector to debug the server:
npx @modelcontextprotocol/inspector \
uv \
--directory . \
run mcp-server-appwrite
Ensure your .env
file is properly configured first. You can access the inspector at http://localhost:5173
.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.