Mcp For Api

io.github.appwrite由 GitHub 帳號 appwrite 發布v0.2.8更新於 Oct 24, 2026

MCP (Model Context Protocol) server for Appwrite

概覽

AI 產生的概覽

Appwrite 的 MCP 伺服器,把 Appwrite 的資料庫、使用者、函式、團隊與儲存等 API 暴露為工具,供助理透過託管 OAuth 端點或本機 stdio 程序呼叫。

可以做什麼
  • 透過 Appwrite API 管理資料庫、集合與文件
  • 管理使用者、團隊及其成員關係
  • 操作 Appwrite 專案中的函式與儲存資源
  • 在助理內檢索 Appwrite 文件
  • 可連接託管的 Appwrite Cloud 伺服器,也可連接自架實例
適用情境
適合在開發或維運 Appwrite 後端時,讓助理在聊天用戶端裡檢視與修改專案資料、使用者、函式或儲存。撰寫 Appwrite 相關程式碼時也可用來查文件。
執行需求
支援遠端 MCP 的用戶端,指向託管的 Appwrite 端點,首次連線需在瀏覽器中完成 OAuth 授權;不支援 OAuth 的用戶端需用 Node.js 透過 npx mcp-remote 橋接。自架 Appwrite 需在本機以 stdio 執行伺服器並提供專案 API 金鑰。僅支援桌面用戶端。
安裝前請注意
工具直接作用於實際的 Appwrite 專案,助理的呼叫可能建立、修改或刪除資料、使用者、團隊、函式與檔案。核准 OAuth 授權頁即向用戶端授予相應權限範圍,請先確認。自架方式需要專案 API 金鑰,屬敏感憑證。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp For Api,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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.

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,提交 11f6060

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.2.8最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

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

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

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

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