Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP (Model Context Protocol) server for Appwrite
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"for-api": {
"command": "uvx",
"args": [
"mcp-server-appwrite"
]
}
}
}在终端中运行这条命令
claude mcp add for-api -- uvx mcp-server-appwrite粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"for-api": {
"command": "uvx",
"args": [
"mcp-server-appwrite"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"for-api": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-server-appwrite"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 appwrite 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.2.8)于13个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, dotnet-mcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
Pick your client below. Each adds the hosted Appwrite Cloud server.
Claude Code
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:
{
"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.
Cursor
Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
{
"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.
VS Code (GitHub Copilot)
Edit .vscode/mcp.json (workspace) or your user configuration via the Command Palette → MCP: Open User Configuration.
{
"servers": { "appwrite": { "type": "http", "url": "https://mcp.appwrite.io/" } } }
Codex
Edit ~/.codex/config.toml.
[mcp_servers.appwrite]
url = "https://mcp.appwrite.io/"
Then authenticate from the terminal:
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):
OpenCode
Edit opencode.json (project) or ~/.config/opencode/opencode.json (global).
{
"$schema": "https://opencode.ai/config.json", "mcp": { "appwrite": { "type": "remote", "url": "https://mcp.appwrite.io/", "enabled": true } } }
Windsurf
Edit ~/.codeium/windsurf/mcp_config.json.
{
"mcpServers": { "appwrite": { "serverUrl": "https://mcp.appwrite.io/" } } }
Gemini CLI
gemini mcp add --transport http appwrite https://mcp.appwrite.io/
Or edit ~/.gemini/settings.json (note the key is httpUrl, not url):
{
"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).
{
"mcpServers": { "appwrite": { "serverUrl": "https://mcp.appwrite.io/" } } }
⚠️ Note: Antigravity strictly requires the
serverUrlkey for remote transport. Using legacy fields likeurlorhttpUrlwill 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
copilot mcp add --transport http appwrite https://mcp.appwrite.io/
Or run /mcp add inside a session, or edit ~/.copilot/mcp-config.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):
{
"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:
{
"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:
{
"mcpServers": { "appwrite": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"] } } }
A browser window opens to authenticate on first connect.
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.
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.
appwrite_search_docs tool and how to rebuild its index.This MCP server is licensed under the MIT License. See the LICENSE file for details.