Appwrite MCP server
The official Appwrite MCP server opens a project databases, users, functions and storage to an agent through OAuth.
- 72 ★ on the repository
- Last commit
Broad access
Why this level
- The agent creates and deletes data, users and functions of the project within granted scopes.
- Changes hit the live project unless the `staging` environment is selected.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/appwrite-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent creates and deletes data, users and functions of the project within granted scopes.
- Changes hit the live project unless the `staging` environment is selected.
This is third-party code. Review the repository files before installing.
What it does
The Appwrite MCP server exposes the platform API as client tools: databases, users, functions, teams, storage and more. The hosted server `https://mcp.appwrite.io/` needs no keys: on first connect the client opens an Appwrite consent screen, you approve the scopes and access is ready. Work in Appwrite Cloud environments such as `staging` goes through `appwrite_get_context` and the `environment_id` parameter. Every write by the agent carries a short `reason` that lands in the project audit log and shows in the Activity tab. A built-in `appwrite_search_docs` tool searches the Appwrite documentation. For your own Appwrite instance the server runs locally over stdio with a project API key.
Who it is for. Developers on Appwrite who let an agent manage the project backend: collections, functions and users.
Good fit when
- An agent creates a collection in a database and sets its attributes.
- You need the list of project users and teams.
- A function is deployed and then its execution log is reviewed.
- Changes are tried in the `staging` environment first.
- The Activity log shows what the agent changed and why.
Not a fit when
- The backend is different: the tools work only with Appwrite.
- The agent must not get write access to the project.
- CI has no browser: cloud sign-in uses OAuth, and CI relies on the self-hosted run with an API key.
Example request
Show the Appwrite project context, environments and database collections, then create a test collection in `staging`.MCP
- Transport
- http, stdio
- Authentication
- OAuth
Limitations
The cloud option needs an Appwrite Cloud account and scope approval in the browser. The agent can create and delete data, users and functions, so grant minimal scopes and try changes in the `staging` environment first. JetBrains AI Assistant, Junie and Cline do not yet support OAuth for remote servers and need the `npx -y mcp-remote https://mcp.appwrite.io/` bridge and Node.js. MCP Events (webhooks on project changes) are marked as in development and not yet available. The license is MIT.
How to disable. Remove the `appwrite` entry from the client configuration (`claude mcp remove appwrite`) and revoke the granted scopes in the Appwrite account.
FAQ
Are API keys needed?
Not in the cloud: sign-in goes through browser OAuth. For your own instance the server runs locally over stdio with a project API key.
Which clients are supported?
Claude Code, Claude Desktop, Cursor, VS Code with Copilot, Codex, OpenCode, Windsurf, Gemini CLI, Antigravity, GitHub Copilot CLI, Zed and Warp. JetBrains and Cline connect through `mcp-remote`.
What is the server address?
`https://mcp.appwrite.io/`. The conventional `https://mcp.appwrite.io/mcp` also works and reaches the same server.
Can it search the documentation?
Yes, the built-in `appwrite_search_docs` tool searches the Appwrite docs in-process, and the index is built by a script.
Where do I see what the agent changed?
Every write by the agent carries a short `reason` that Appwrite records in the project audit log. Review changes on the project Activity tab.
Discussion
No questions or reviews yet.
Related
MCP serversApollo's MCP server: turns chosen GraphQL operations into tools the agent uses to work with your API
MCP server for the InsForge backend: the agent creates tables, buckets and edge functions and ships the app from the editor
Supabase's official MCP server: the agent manages tables, reads project config and queries data after an OAuth login
FireCMS Cloud MCP server: an agent reads Firestore data, infers collection schemas and manages the project's users.
Firebase MCP Server
Firebase CLI and MCP Server
Official Firebase MCP server from the Firebase CLI: projects, Firestore, Auth, Crashlytics, Remote Config and function logs
Rebase MCP server: the agent edits the schema, documents and users of a Postgres backend, with writes limited to localhost
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Appwrite MCP server (this card) | yes | OAuth | 72 | |
| Supabase MCP Server | yes | OAuth | 3,008 | manages a Supabase project; Appwrite MCP works with an Appwrite project and writes the reason of each change to the audit log |
| Firebase MCP Server | yes | OAuth | 4,490 | serves Firebase; here the Appwrite cloud server with OAuth and environments |
README in short
The server is written in Python (`mcp_server_appwrite`) and the docs index is built by a script. The README has setup for a dozen clients, and separate pages describe the tool set, OAuth sign-in and self-hosting.