Appwrite

io.github.appwrite由 GitHub 帳號 appwrite 發布v2.4.3更新於 Nov 7, 2026

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

已驗證Streamable HTTP可網頁執行資料庫雲端與基礎設施開發者工具

概覽

AI 產生的概覽

Appwrite 的 MCP 伺服器讓助理建置與管理 Appwrite 後端:驗證、資料庫、儲存、函式、團隊與託管。

可以做什麼
  • 管理資料庫及其紀錄,包含 Postgres、MySQL 與向量資料庫
  • 處理使用者、團隊與驗證設定
  • 建立與部署函式及託管,並管理儲存與 CDN 資源
  • 查詢 Appwrite 文件並列出專案環境
  • 每次寫入都附帶原因,記錄在專案的稽核日誌中
適用情境
適合在使用 Appwrite 時讓助理檢視或修改專案資源(資料、使用者、函式、儲存),或不必離開對話就能查閱 Appwrite 文件。也適合在 staging 等不同專案環境中運作的代理。
執行需求
使用 mcp.appwrite.io 遠端端點,透過瀏覽器 OAuth 同意畫面授權並核准對應的權限範圍;Cloud 不需複製 API 金鑰。不支援遠端 OAuth 的用戶端(部分方案的 Claude Desktop、JetBrains、Cline)需要 Node.js,透過 npx mcp-remote 橋接。自架 Appwrite 需在本機以 stdio 執行伺服器並使用專案 API 金鑰。
安裝前請注意
代理可以寫入你的 Appwrite 專案——建立、修改或刪除資料、使用者、函式與儲存,請仔細審核授權的權限範圍,並在 Activity 分頁查看記錄的原因。OAuth 會授予對你 Appwrite 帳號的存取權;自架方式使用專案 API 金鑰,屬於敏感憑證。事件/Webhook 功能標示為尚未提供。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Appwrite,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.appwrite%2Fmcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

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

來源:README.md,提交 c87ac65

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

42
  1. v2.4.3最新Nov 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

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分