Skip to main content

Appwrite MCP server

MCP Registry Version

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.

Reasons and environments

Every write the agent makes carries a short reason (why it made the change). Appwrite records it on the project's audit log, so you can review what your agent changed, and why, in the project's Activity tab.

On Appwrite Cloud, the agent can act in a project's environments (for example staging): appwrite_get_context lists them, and each call takes the environment's ID as environment_id next to the project's project_id. See Tool surface.

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

License

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

Metadata

Release files for mcp-server-appwrite 2.4.3

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 2.4.3
File Size Uploaded Provenance Actions
mcp_server_appwrite-2.4.3.tar.gz 37.2 MB Without provenance Details for mcp_server_appwrite-2.4.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mcp-server-appwrite 2.4.3
File Interpreter ABI Platform Actions
mcp_server_appwrite-2.4.3-py3-none-any.whl Python 3 none any Details for mcp_server_appwrite-2.4.3-py3-none-any.whl

Total release size: 73.5 MB

Release files / mcp_server_appwrite-2.4.3.tar.gz

Download URL mcp_server_appwrite-2.4.3.tar.gz
Size 37.2 MB
Tags Source
SHA-256 checksum
How to use checksums
563cf06cf98463f4c08d24260550f642885411fd904ee033eb09bd2e2b3603d8
BLAKE2b-256 checksum
How to use checksums
a6b1251ea17446aa7fcddd2a4fd374072e97a500d6710a9a8b7a06706a603449
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.16

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

Download URL mcp_server_appwrite-2.4.3-py3-none-any.whl
Size 36.3 MB
Tags Python 3
SHA-256 checksum
How to use checksums
8e1bb9f34484c6f18ebcd9c552ef7774e5e5fb741ef0faf7dba9a6bce935a49e
BLAKE2b-256 checksum
How to use checksums
ce7a43c1ec591175a75890de727725a2ff993bde9959739221a09fc403db39cf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.16

Security for mcp-server-appwrite 2.4.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

2.4.3 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page