← Back to directory

Appwrite MCP Server

Official

Operate your Appwrite backend through your MCP client.

GitHub source repository ↗

★ 71 Stars Category · Dev Tools Popular Source revision b2e4d51bff5c

63FMRS · C

Reliability

8/20

Security and permissions

12/20

Maintenance

13/20

Documentation

16/20

Setup experience

14/20

An official, Appwrite-maintained MCP server that lets many MCP clients manage Appwrite databases, users, functions, teams, and storage via a hosted OAuth endpoint or a self-hosted stdio option.

Read the FMRS scoring method →

The official Model Context Protocol server for Appwrite, exposing its API — databases, users, functions, teams, storage, and more — as callable tools. Connect to a hosted, browser-authenticated OAuth endpoint, or run it locally over stdio against a self-hosted Appwrite instance using a project API key.

Tools

appwrite_search_docs

An in-process tool for searching Appwrite documentation to answer questions about the platform's APIs and features.

Setup

Add the hosted endpoint https://mcp.appwrite.io/ (the /mcp path also works) as a remote/HTTP MCP server in a supporting client, then approve the Appwrite OAuth consent screen in your browser on first connect — no keys to copy. Clients without native remote-MCP/OAuth support (e.g., JetBrains, Cline) can bridge it over stdio with npx -y mcp-remote https://mcp.appwrite.io/. For self-hosted Appwrite, run the server locally over stdio and authenticate with a project API key (see docs/self-hosted.md).

claude_desktop_config.json

{"mcpServers":{"appwrite":{"url":"https://mcp.appwrite.io/"}}}

Generate and validate client config

Fit and risk

Best for

Developers already on Appwrite Cloud who want AI-assisted backend administration
Teams that prefer browser-authenticated OAuth scopes over managing API keys
Self-hosted Appwrite operators who can run a local stdio bridge with a project API key

Not for

Users without an Appwrite project or account
Clients that lack remote MCP/OAuth support and cannot install Node.js for the mcp-remote bridge
Non-Appwrite backend workflows

Required permissions

OAuth scopes approved during the browser consent flow (covering databases, users, functions, teams, storage, etc.)
For self-hosted use, an Appwrite project API key with permissions matching the operations invoked

Risks and side effects

Broad backend access (databases, users, functions, storage) if overly broad OAuth scopes or an overly permissive API key are granted
Destructive operations (deleting data, modifying users/teams) are possible if the AI client is given write scopes
The hosted server is a third-party (Appwrite-operated) service brokering requests to your Appwrite project

Troubleshooting

Confirm the client supports remote/HTTP MCP servers and OAuth; otherwise use the mcp-remote stdio bridge
Re-run the browser authentication flow if the consent screen doesn't appear or the connection fails
On Claude Desktop Team/Enterprise plans, only an organization Owner can add custom connectors
For self-hosted setups, verify the project API key and check docs/self-hosted.md for per-client configuration
Check docs/tool-surface.md for the exact tools exposed if a call is unavailable

Use cases

Managing Appwrite databases, collections, and documents from an AI assistant

Creating and inspecting Appwrite users and teams via natural language

Deploying and managing Appwrite functions

Searching Appwrite documentation in-process

Automating Appwrite storage/bucket operations

Supported clients

Claude CodeFull support

Claude DesktopFull support

CursorFull support

VS CodeFull support

CodexFull support

OpenCodeFull support

WindsurfFull support

Gemini CLIFull support

AntigravityFull support

GitHub Copilot CLIFull support

ZedFull support

WarpFull support

JetBrains AI Assistant / JuniePartial support

ClinePartial support

Related MCP servers

Compare with other MCP servers