OfficialVerified

Appwrite MCP Server

Appwrite API databases, users, functions, and storage access for your AI assistant.

Data last scanned today · Reviewed today

714 tools★ 72PythonMIT

Overview

This server provides a bridge to Appwrite backend services, enabling your MCP client to interact with databases, user management, storage, functions, and teams. It utilizes an OAuth flow where you authenticate through a browser consent screen during the initial connection process, eliminating the need for manual API key management.

Our verdict

This server carries a high risk level (43/100) and should be used with caution. Crucially, the authentication method and read-only mode support have not yet been editorially reviewed, meaning there is no verified assurance on how data permissions are handled. It is recommended for developers who understand the implications of connecting external AI tools to their Appwrite backend, particularly as it is a community-maintained project rather than an official vendor release.

Zero direct dependencies reduces the supply-chain attack surface
Active development evidenced by recent daily commits
Supports 11 contributors, which mitigates individual bus-factor risk
Open source project under the MIT license

Security score is low at 43/100
Authentication mechanism lacks editorial verification
Read-only operational modes remain unreviewed
Not maintained by the official Appwrite vendor

Tools

Tool	Description	Risk
appwrite_get_context	Workspace summary. API key → project + readable service totals/samples. OAuth → also account, organization, discovered projects.	low
appwrite_search_tools	Searches the internal catalog at runtime.	low
appwrite_call_tool	Invokes a catalog tool. Mutating calls require confirm_write=true.	medium
appwrite_search_docs	Semantic search over Appwrite docs.	low

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›How do I authenticate with the Appwrite MCP server?

Authentication is handled automatically via a browser-based OAuth flow. The first time you connect, your client will open an Appwrite consent screen where you approve the necessary scopes; there are no API keys to copy.

›What happens if I cannot add the server as a custom connector in Claude Desktop?

If you are on a free plan or a restricted Team/Enterprise account, you can bridge the remote server through stdio. You must have Node.js installed to use the provided npx command in your local MCP server configuration.

›Which Appwrite services are accessible through this server?

The server exposes tools for interacting with Appwrite databases, users, functions, teams, storage, and other core API resources.

›Do I need to manage tokens or headers manually?

No, authentication is handled through your browser. For clients like Codex, you should leave the token and header fields empty when adding the server URL.

›How do I re-authenticate if my session expires?

For clients like the Gemini CLI, you can trigger re-authentication by running the command /mcp auth appwrite inside an active session.