Appwrite MCP server

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.

How the Appwrite MCP server handles OAuth and scopes

Connect your client

Pick your client below. Each adds the hosted Appwrite Cloud server.

Claude Code

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.

Claude Desktop

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.

Appwrite server running under Local MCP servers in Claude Desktop

Cursor

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.

Appwrite server connected in Cursor's MCP settings

VS Code (GitHub Copilot)

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/"
    }
  }
}

Codex

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):

Appwrite MCP server settings in the Codex GUI

OpenCode

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
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json.

{
  "mcpServers": {
    "appwrite": {
      "serverUrl": "https://mcp.appwrite.io/"
    }
  }
}

Gemini CLI

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.

Antigravity (CLI & 2.0)

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 serverUrl key for remote transport. Using legacy fields like url or httpUrl will 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.

GitHub Copilot CLI

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.

Zed

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.

Warp

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 AI Assistant / Junie

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

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.

Self-hosted Appwrite

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.

Documentation

Tool surface — the tools exposed to the model and the internal Appwrite catalog.
How Cloud authentication works — the OAuth 2.1 flow.
Documentation search — the in-process appwrite_search_docs tool and how to rebuild its index.
Self-hosted Appwrite — run the server locally with a project API key.
Local development — running, testing, and debugging the server locally.
AGENTS.md — full contributor guide and pre-PR checklist.

License

This MCP server is licensed under the MIT License. See the LICENSE file for details.

Release files for mcp-server-appwrite 0.10.13

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-server-appwrite 0.10.13
File	Size	Uploaded
mcp_server_appwrite-0.10.13.tar.gz	32.8 MB	Sep 16, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for mcp-server-appwrite 0.10.13
File	Interpreter	ABI	Platform	Reset
mcp_server_appwrite-0.10.13-py3-none-any.whl 31.9 MB Sep 16, 2026	Python 3	none	any	Details

Total release size: 64.7 MB

Release files / mcp_server_appwrite-0.10.13.tar.gz

Download URL	mcp_server_appwrite-0.10.13.tar.gz
Size	32.8 MB
Tags	Source
SHA-256 checksum How to use checksums	`a0148f9102447d3747c04afae335f146a7520933301aeb70c1c47b9ed5899642`
BLAKE2b-256 checksum How to use checksums	`576d10f71c9e1dd8d354ac94209c572467b081a13d89529f4357e3c5c8ae0537`
Upload date	Sep 16, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.12.14`

Release files / mcp_server_appwrite-0.10.13-py3-none-any.whl

Download URL	mcp_server_appwrite-0.10.13-py3-none-any.whl
Size	31.9 MB
Tags	Python 3
SHA-256 checksum How to use checksums	`2e38efd6df884b89155823c21d3c8c3ab3a394a1fdecbc6e042757bf299cd90e`
BLAKE2b-256 checksum How to use checksums	`9d153c59580cb15f9897d95e503cfba56134c32c97e8147476f9b26187c8b21a`
Upload date	Sep 16, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.12.14`