Appwrite MCP

What appwrite/mcp MCP server does

The appwrite/mcp MCP server makes Appwrite operations available to an AI agent through the Model Context Protocol. The exposed Appwrite API covers databases, users, functions, teams, storage, messaging, and other Appwrite capabilities described by the server. It also includes an in-process appwrite_search_docs tool for searching Appwrite documentation.

This is a fit for projects that already use Appwrite and need an MCP client to work with backend resources through natural-language requests. It is also useful when an agent needs Appwrite-specific documentation while planning or troubleshooting an operation.

How it works

The default connection is a hosted HTTP service at https://mcp.appwrite.io/. The conventional https://mcp.appwrite.io/mcp URL points to the same hosted server. On first connection, the MCP client opens an Appwrite consent screen in a browser. After the user approves the requested scopes, the client can call the available tools without requiring manually copied keys.

The appwrite/mcp MCP server can also run locally for a self-managed Appwrite installation. In that mode, the server uses stdio transport and authenticates with a project API key. The repository provides separate self-hosted guidance for configuring individual clients.

Setup and configuration

For hosted use, add the remote URL to the MCP client’s server configuration. The README documents direct HTTP configuration for clients including Claude Desktop, Cursor, Windsurf, and several command-line or editor clients. Some clients that do not support OAuth for remote MCP servers can connect through a local stdio bridge using Node.js and mcp-remote; that bridge is a client configuration method, not the Appwrite server itself.

Hosted authentication is completed in the browser. Client configuration should therefore use the server URL and should not include an API token or header. For self-hosting, follow the repository’s self-hosted instructions and supply a project API key; the provided material does not specify a single universal launch command or environment-variable name.

Tools and capabilities

The appwrite/mcp MCP server provides access to Appwrite areas including:

• Databases
• Users and authentication-related backend management
• Functions
• Teams
• Storage
• Messaging
• Appwrite documentation search through appwrite_search_docs

The exact tool surface is maintained separately in the repository’s tool-surface documentation. The server is intended for clients that can register remote HTTP MCP servers or, where necessary, connect through stdio.

Limitations and notes

OAuth support depends on the MCP client. The README identifies clients that can connect directly and notes that some clients require the stdio bridge. Hosted access uses OAuth scopes and an Appwrite consent step, while self-hosted operation requires a project API key. The supplied material does not establish a separate hosted pricing tier or describe permissions for each individual tool, so those details should be checked in Appwrite’s current documentation and consent flow.