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 分