About Appwrite MCP server
Appwrite MCP server is Appwrite's own MCP server, exposing its API for databases, users, functions, teams and storage as tools for MCP clients. Users connect to the hosted server and authenticate through the browser without copying keys. It can also run locally for self-hosted Appwrite instances.
Key features
- 01Hosted server with browser-based sign-in
- 02Tools covering databases, users, functions, teams and storage
- 03Setup guides for many MCP clients
- 04Documentation search tool appwrite_search_docs
- 05Local stdio mode for self-hosted Appwrite with API keys
Use cases
- 01Managing an Appwrite backend project through an AI assistant
- 02Querying Appwrite data and configuration from an IDE or CLI client
- 03Running the server locally against a self-hosted Appwrite instance
MCP support
This is an MCP server that exposes Appwrite API operations as tools to MCP clients, using OAuth 2.1 for cloud authentication.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.appwrite.io/mcpclaude mcp add --transport http appwrite https://mcp.appwrite.io/mcp{"mcpServers":{"appwrite":{"type":"http","url":"https://mcp.appwrite.io/mcp"}}}Open in Cursor{"servers":{"appwrite":{"type":"http","url":"https://mcp.appwrite.io/mcp"}}}Open in VS Code{"mcpServers":{"appwrite":{"type":"http","url":"https://mcp.appwrite.io/mcp"}}}{"mcpServers":{"appwrite":{"serverUrl":"https://mcp.appwrite.io/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEAppwrite MCP server
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.

Connect your client
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.
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
- Tool surface — the tools exposed to the model and the internal Appwrite catalog.
- How Cloud authentication works — the OAuth 2.1 flow.
- Documentation search — the in-process
appwrite_search_docstool and how to rebuild its index. - Events — MCP Events: webhook subscriptions to changes in your Appwrite project (in development, not available yet).
- Self-hosted Appwrite — run the server locally with a project API key.
- Local development — running, testing, and debugging the server locally.
- AGENTS.md — full contributor guide and pre-PR checklist.
License
This MCP server is licensed under the MIT License. See the LICENSE file for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.