Connects Claude to your Appwrite backend through a two-tool interface that searches and calls the full Appwrite API catalog at runtime. Instead of exposing hundreds of individual tools, you get appwrite_search_tools and appwrite_call_tool that dynamically access databases, users, functions, teams, and storage operations. Large responses are stored as MCP resources with preview text to keep context manageable. Write operations require explicit confirmation. Requires an Appwrite project ID and API key with appropriate scopes, which the server validates on startup rather than failing silently later. Useful when you're building or debugging Appwrite applications and want to query collections, manage users, or inspect function logs without switching to the console or writing one-off scripts.
A Model Context Protocol server for Appwrite. It exposes Appwrite's API — databases, users, functions, teams, storage, and more — as tools your MCP client can call.
Connect to the hosted server at https://mcp.appwrite.io/ and authenticate
through your browser. The first time you connect, your client opens an Appwrite
consent screen; approve the scopes and you're connected. There are no keys to
copy. The conventional https://mcp.appwrite.io/mcp URL is also supported and
connects to the same server.

Pick your client below. Each adds the hosted Appwrite Cloud server.
claude mcp add --transport http appwrite https://mcp.appwrite.io/
Then, inside a Claude Code session, run /mcp, select appwrite, and follow
the browser prompt to authenticate.
Go to Settings → Connectors → Add custom connector and paste
https://mcp.appwrite.io/. Available on Pro and Max plans; on Team and
Enterprise plans only an organization Owner can add custom connectors.
If you don't see that option (free plan, or a Team/Enterprise member), bridge the remote server through stdio instead (requires Node.js). Go to Settings → Developer → Local MCP servers, click Edit Config, and add:
{
"mcpServers": {
"appwrite": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]
}
}
}
Restart Claude Desktop; the server appears under Local MCP servers and a browser window opens to authenticate.

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
{
"mcpServers": {
"appwrite": {
"url": "https://mcp.appwrite.io/"
}
}
}
Cursor prompts you to log in through the browser; the server then shows up under Settings → MCP with its tools enabled.

Edit .vscode/mcp.json (workspace) or your user configuration via the Command
Palette → MCP: Open User Configuration.
{
"servers": {
"appwrite": {
"type": "http",
"url": "https://mcp.appwrite.io/"
}
}
}
Edit ~/.codex/config.toml.
[mcp_servers.appwrite]
url = "https://mcp.appwrite.io/"
Then authenticate from the terminal:
codex mcp login appwrite
In the Codex GUI, you can instead add the server from the MCP settings —
set the URL to https://mcp.appwrite.io/ and leave the token and header
fields empty (authentication happens through the browser):

Edit opencode.json (project) or ~/.config/opencode/opencode.json (global).
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"appwrite": {
"type": "remote",
"url": "https://mcp.appwrite.io/",
"enabled": true
}
}
}
Edit ~/.codeium/windsurf/mcp_config.json.
{
"mcpServers": {
"appwrite": {
"serverUrl": "https://mcp.appwrite.io/"
}
}
}
gemini mcp add --transport http appwrite https://mcp.appwrite.io/
Or edit ~/.gemini/settings.json (note the key is httpUrl, not url):
{
"mcpServers": {
"appwrite": {
"httpUrl": "https://mcp.appwrite.io/"
}
}
}
Gemini CLI opens the browser OAuth flow automatically on first connect. To
re-authenticate, run /mcp auth appwrite inside a session.
Edit ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (project workspace).
{
"mcpServers": {
"appwrite": {
"serverUrl": "https://mcp.appwrite.io/"
}
}
}
⚠️ Note: Antigravity strictly requires the
serverUrlkey for remote transport. Using legacy fields likeurlorhttpUrlwill cause tool registration to fail silently.
Antigravity opens the browser OAuth flow automatically on first connect. If you manually edit the JSON file, navigate to Settings → Customizations → Installed MCP Servers and click Refresh to reload the tool definitions.
copilot mcp add --transport http appwrite https://mcp.appwrite.io/
Or run /mcp add inside a session, or edit ~/.copilot/mcp-config.json:
{
"mcpServers": {
"appwrite": {
"type": "http",
"url": "https://mcp.appwrite.io/"
}
}
}
A browser window opens to authenticate on first connect. Check status with
/mcp.
Go to Settings → AI → MCP Servers → Add Server → Add Remote Server, or add
to your settings.json (zed: open settings):
{
"context_servers": {
"appwrite": {
"url": "https://mcp.appwrite.io/"
}
}
}
Zed prompts you to authenticate through the browser on first connect.
Go to Settings → Agents → MCP servers → + Add, choose the URL-based
server type, and enter https://mcp.appwrite.io/.
Warp opens a browser window to authenticate on first connect.
JetBrains IDEs don't yet support OAuth for remote MCP servers, so bridge through stdio (requires Node.js). Go to Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add, switch to the JSON view, and paste:
{
"mcpServers": {
"appwrite": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]
}
}
}
A browser window opens to authenticate on first connect.
Cline doesn't yet support OAuth for remote MCP servers, so bridge through stdio (requires Node.js). In the Cline panel, open the MCP Servers icon → Configure tab → Configure MCP Servers, and add:
{
"mcpServers": {
"appwrite": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]
}
}
}
A browser window opens to authenticate on first connect.
Running your own Appwrite instance? Run the MCP server locally over stdio and
authenticate with a project API key. See docs/self-hosted.md
for per-client setup.
appwrite_search_docs tool and how to rebuild its index.This MCP server is licensed under the MIT License. See the LICENSE file for details.