# appwrite/mcp [Official] [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/appwrite/mcp  
**GitHub Stars:** 72  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/appwrite-mcp

## Description
Official Appwrite MCP server. Connect via hosted OAuth at https://mcp.appwrite.io/ (no API keys) or self-host with a project API key to manage databases, auth, users, functions, storage, messaging, and more.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

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

## Documentation

## What appwrite/mcp does

appwrite/mcp exposes Appwrite functionality through the Model Context Protocol. Its tool surface covers Appwrite services including databases, users, functions, teams, storage, messaging, authentication, and other API resources. This lets an MCP client present Appwrite operations to an AI agent without requiring the agent to use Appwrite's HTTP API directly.

The server is suitable for tasks that involve managing Appwrite project resources through an AI-assisted development workflow. Access is controlled through the selected authentication method and the scopes granted during authorization.

## How it works

The hosted service is available at `https://mcp.appwrite.io/`. The conventional `/mcp` path is also supported and points to the same service. Remote clients connect over HTTP and begin an OAuth flow in the browser. During the first connection, Appwrite displays a consent screen where the user approves the requested scopes; no API key needs to be copied into the client configuration.

For a self-managed Appwrite installation, the server can run locally over stdio. That mode authenticates with a project API key and is intended for connections to an instance you operate yourself.

## Setup and configuration

For hosted use, add `https://mcp.appwrite.io/` as a remote MCP server in a compatible client, then complete the browser authentication prompt. Clients with documented connection procedures include Claude Code, Claude Desktop, Cursor, VS Code with GitHub Copilot, Codex, Windsurf, Gemini CLI, Zed, JetBrains AI Assistant or Junie, and Cline.

Claude Desktop and JetBrains AI Assistant or Junie can use the hosted service through an `mcp-remote` stdio bridge when direct remote OAuth is unavailable. Cline likewise uses that bridge and requires Node.js. Codex can authenticate from the terminal with `codex mcp login appwrite`, while Gemini CLI supports reauthentication through `/mcp auth appwrite`.

Self-hosted deployments require a local server process and a project API key. Client-specific self-hosting instructions are provided by the project.

## Tools and capabilities

The exposed Appwrite API surface includes operations for:

- Databases
- Authentication and users
- Functions
- Teams
- Storage
- Messaging
- Other Appwrite services and resources

The project also documents an in-process `appwrite_search_docs` tool for searching Appwrite documentation.

## Limitations and notes

Hosted OAuth support varies by client. JetBrains AI Assistant or Junie and Cline do not support OAuth for remote MCP servers directly, so they require the stdio bridge. Claude Desktop may require a supported plan or organization permissions for custom remote connectors.

MCP Events, described as webhook subscriptions for project changes, are still in development and are not available. The hosted service and self-hosted mode use different authentication approaches: browser OAuth for the former and a project API key for the latter.

_Full upstream README: https://allmcps.com/mcp/appwrite-mcp/readme_