Appwrite

io.github.appwritePublished by GitHub account appwritev2.4.3Updated Nov 7, 2026

Build and deploy backends: auth, Postgres/MySQL/vector databases, storage, functions, hosting, CDN

VerifiedStreamable HTTPWeb executableDatabasesCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Appwrite's MCP server lets an assistant build and manage Appwrite backends: auth, databases, storage, functions, teams and hosting.

What you can do
  • Manage databases and their records, including Postgres, MySQL and vector databases
  • Handle users, teams and authentication settings
  • Create and deploy functions and hosting, with storage and CDN resources
  • Look up Appwrite documentation and list project environments
  • Every write carries a reason that is recorded in the project's audit log
When to use it
Useful when you work in Appwrite and want an assistant to inspect or change project resources — data, users, functions, storage — or to look up Appwrite docs without leaving the chat. Also suited to agents acting across staging and other project environments.
Requirements
Remote endpoint at mcp.appwrite.io, authenticated through a browser OAuth consent screen with scopes you approve; no API keys to copy for Cloud. Clients without remote OAuth support (Claude Desktop on some plans, JetBrains, Cline) need Node.js to bridge via npx mcp-remote. Self-hosted Appwrite requires running the server locally over stdio with a project API key.
Before you install
The agent can write to your Appwrite project — creating, changing or deleting data, users, functions and storage — so review the scopes you approve and the recorded reasons in the Activity tab. Access is granted to your Appwrite account through OAuth; self-hosted setups use a project API key, which is a sensitive credential. Events/webhooks are noted as not yet available.

Installation

In SourceWeft

  1. Open Appwrite in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.appwrite%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "appwrite": {
      "type": "http",
      "url": "https://mcp.appwrite.io/"
    }
  }
}

README

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

json
{  "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).

json
{  "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.

json
{  "servers": {    "appwrite": {      "type": "http",      "url": "https://mcp.appwrite.io/"    }  }}
Codex

Edit ~/.codex/config.toml.

toml
[mcp_servers.appwrite]url = "https://mcp.appwrite.io/"

Then authenticate from the terminal:

bash
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).

json
{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "appwrite": {      "type": "remote",      "url": "https://mcp.appwrite.io/",      "enabled": true    }  }}
Windsurf

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

json
{  "mcpServers": {    "appwrite": {      "serverUrl": "https://mcp.appwrite.io/"    }  }}
Gemini CLI
bash
gemini mcp add --transport http appwrite https://mcp.appwrite.io/

Or edit ~/.gemini/settings.json (note the key is httpUrl, not url):

json
{  "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).

json
{  "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
bash
copilot mcp add --transport http appwrite https://mcp.appwrite.io/

Or run /mcp add inside a session, or edit ~/.copilot/mcp-config.json:

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

json
{  "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:

json
{  "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:

json
{  "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.

Source: README.md at commit c87ac65

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

42
  1. v2.4.3LatestNov 7, 2026
  2. v2.4.2Nov 6, 2026
  3. v2.4.1Nov 5, 2026
  4. v2.4.0Nov 4, 2026
  5. v2.3.1Nov 4, 2026
  6. v2.3.0Nov 3, 2026
  7. v2.2.3Oct 31, 2026
  8. v2.2.2Oct 30, 2026
  9. v2.2.1Oct 29, 2026
  10. v1.0.26Oct 25, 2026
  11. v1.0.25Oct 24, 2026
  12. v1.0.24Oct 23, 2026
  13. v1.0.23Oct 22, 2026
  14. v1.0.22Oct 21, 2026
  15. v1.0.21Oct 20, 2026
  16. v1.0.20Oct 19, 2026
  17. v1.0.19Oct 17, 2026
  18. v1.0.18Oct 16, 2026
  19. v1.0.17Oct 15, 2026
  20. v1.0.16Oct 15, 2026
  21. v1.0.15Oct 14, 2026
  22. v1.0.14Oct 13, 2026
  23. v1.0.13Oct 13, 2026
  24. v1.0.12Oct 12, 2026
  25. v1.0.10Oct 9, 2026
  26. v1.0.9Oct 9, 2026
  27. v1.0.7Oct 8, 2026
  28. v1.0.6Oct 7, 2026
  29. v1.0.5Oct 6, 2026
  30. v1.0.3Oct 6, 2026
  31. v1.0.2Oct 2, 2026
  32. v1.0.1Oct 1, 2026
  33. v1.0.0Oct 1, 2026
  34. v0.10.21Sep 30, 2026
  35. v0.10.20Sep 29, 2026
  36. v0.10.19Sep 26, 2026
  37. v0.10.18Sep 25, 2026
  38. v0.10.17Sep 24, 2026
  39. v0.10.16Sep 23, 2026
  40. v0.10.15Sep 22, 2026
  41. v0.10.14Sep 19, 2026
  42. v0.10.13Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts