How to connect the Appwrite MCP server

Before you start

• An Appwrite Cloud account with a project. The hosted server works only with Appwrite Cloud; self-hosted instances use the local server with an API key instead. appwrite.io/docs

Authentication

Your client → Appwrite MCP

OAuth sign-in, handled by your MCP client. appwrite.io/docsgithub.com/appwritemodelcontextprotocol.io/specification

Appwrite MCP → Appwrite API

The server acts on your account with the access you approve. github.com/appwrite

Steps

1. Open Appwrite's MCP server setup instructions for your client

   appwrite.io/docs/tooling/ai/mcp-servers/api
2. Add the Appwrite MCP server to your client

   Add https://mcp.appwrite.io/ as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"). The path /mcp is an alias for the same server. Clients without OAuth support for remote servers, such as JetBrains AI Assistant and Cline, connect through the mcp-remote bridge, which needs Node.js.

   appwrite.io/docsgithub.com/appwritegithub.com/appwriteregistry.modelcontextprotocol.io/v0.1
3. Sign in to Appwrite and approve the requested scopes on the consent screen
   appwrite.io/docsgithub.com/appwrite
4. On a machine without a browser, finish sign-in from your local browser

   The OAuth redirect goes to a localhost callback on the machine that runs the client. Over SSH or on a remote host, open the sign-in URL the client prints in your local browser, approve access, then paste the full localhost callback URL back into the client.

   appwrite.io/docs
5. List the server's tools

   Your client should list the server's tools. That confirms the connection, not every API permission.

   github.com/appwrite

What we observed

• 5 Nov 2026: HTTP 401 with WWW-Authenticate resource_metadata https://mcp.appwrite.io/.well-known/oauth-protected-resource, which names the authorization server https://fra.cloud.appwrite.io/v1/oauth2/console and a long list of project and organization scopes.