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 分