Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP (Model Context Protocol) server for Appwrite
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"for-api": {
"command": "uvx",
"args": [
"mcp-server-appwrite"
]
}
}
}Run this in your terminal
claude mcp add for-api -- uvx mcp-server-appwritePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"for-api": {
"command": "uvx",
"args": [
"mcp-server-appwrite"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"for-api": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-server-appwrite"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account appwrite, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.8) reached the registry 13 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.