Appwrite MCP Server for Claude
Connect Claude to the full Appwrite backend platform — databases, authentication, serverless functions, teams, messaging, and storage — with the official Appwrite MCP server using dynamic dispatch across the entire Appwrite API surface.
Open the source and read safety notes before installing.
Safety notes
- Mutation operations (write, update, delete) require `confirm_write=true` to be passed explicitly, adding a confirmation step before any destructive action.
- The API key scope determines what operations are available — use least-privilege scopes for your use case.
Privacy notes
- User records, database documents, function logs, team memberships, and messaging data from your Appwrite project are surfaced in Claude's context.
- Your `APPWRITE_API_KEY` grants project-level access — keep it in the MCP config env and never commit it to version control.
Prerequisites
- An Appwrite account — log in at cloud.appwrite.io or self-hosted.
- An Appwrite project with an API key that has the required scopes for your use case.
- Python with `uvx` available.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://appwrite.io
Full copyable content
{
"mcpServers": {
"appwrite": {
"command": "uvx",
"args": ["mcp-server-appwrite"],
"env": {
"APPWRITE_PROJECT_ID": "<project-id>",
"APPWRITE_API_KEY": "<api-key>"
}
}
}
}About this resource
Overview
The Appwrite MCP Server is the official Model Context Protocol server from Appwrite, the
open-source backend-as-a-service platform. Rather than mapping one MCP tool per API endpoint
(which would produce hundreds of tools), it uses a two-tool dynamic dispatch architecture:
appwrite_search_tools discovers what's available, and appwrite_call_tool executes any
Appwrite API operation — covering Databases, Users/Auth, Functions, Teams, Messaging, and
Storage. Mutation operations require explicit confirm_write=true. Python 3.12+, MIT licensed.
Key capabilities
- Databases — create collections, insert/query/update/delete documents.
- Auth/Users — manage users, sessions, and authentication providers.
- Serverless Functions — create, deploy, and invoke functions; read logs.
- Teams — manage team memberships and roles.
- Messaging — check message delivery status across email, SMS, and push.
- Storage — manage buckets and files.
Tools
| Tool | Purpose |
|---|---|
appwrite_search_tools |
Discover available Appwrite API operations |
appwrite_call_tool |
Execute any Appwrite API operation (pass confirm_write=true for mutations) |
The two-tool design keeps MCP tool selection fast while covering the full Appwrite API surface via dynamic dispatch internally.
How it compares
| Server | Database | Auth | Functions | Storage | Notes |
|---|---|---|---|---|---|
| Appwrite MCP | Yes | Yes | Yes | Yes | Official, full platform |
| Firebase MCP | Yes | Yes | No | Yes | Firebase/Google |
| Supabase MCP | Yes | Yes | Yes (Edge) | Yes | Official |
| PocketBase MCP | Yes | Yes | No | No | Community |
Appwrite MCP is the official Appwrite server with full platform coverage via dynamic dispatch, including mutation confirmation for safety.
Installation
Claude Code
claude mcp add appwrite \
-e APPWRITE_PROJECT_ID=<project-id> \
-e APPWRITE_API_KEY=<api-key> \
-- uvx mcp-server-appwrite
For self-hosted Appwrite, add -e APPWRITE_ENDPOINT=https://your-appwrite.example.com/v1.
Claude Desktop
{
"mcpServers": {
"appwrite": {
"command": "uvx",
"args": ["mcp-server-appwrite"],
"env": {
"APPWRITE_PROJECT_ID": "<project-id>",
"APPWRITE_API_KEY": "<api-key>"
}
}
}
}
Get your API key from the Appwrite Console → Project → Settings → API Keys.
Requirements
- Appwrite project (cloud.appwrite.io or self-hosted).
- API key with appropriate scopes.
- Python 3.12+ with
uvx(fromuv). - An MCP client (Claude Code or Claude Desktop).
Security
- Use least-privilege API key scopes — only grant access to the services you need.
- All mutations require
confirm_write=true— Claude will not silently modify data. - Keep
APPWRITE_API_KEYin the MCP config env; never commit it to version control.
Source Verification Notes
Verified on 2026-06-18:
- Official repository
appwrite/mcp-for-api(MIT) on PyPI asmcp-server-appwrite(v0.4.1) documents theuvx mcp-server-appwriteinstall,APPWRITE_PROJECT_ID/APPWRITE_API_KEY/APPWRITE_ENDPOINTconfiguration, two-tool dynamic dispatch architecture (appwrite_search_toolsandappwrite_call_tool),confirm_write=truemutation confirmation, and coverage of Databases, Users, Functions, Teams, Messaging, and Storage. - Claude Code MCP documentation at
code.claude.com/docs/en/mcpdescribes the stdio connector pattern used above.
Source citations
Add this badge to your README
How it compares
Appwrite MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Appwrite MCP Server for Claude Connect Claude to the full Appwrite backend platform — databases, authentication, serverless functions, teams, messaging, and storage — with the official Appwrite MCP server using dynamic dispatch across the entire Appwrite API surface. Open dossier | MCP SQLite Server for Claude Read and write any local SQLite database from Claude — get database info, list tables, inspect schemas, create/read/update/delete records, and run raw SQL queries — with the MCP SQLite server that connects to any `.db` file you specify. Open dossier | Teradata MCP Server for Claude Connect Claude to Teradata — list databases and tables, inspect DDL, run SQL queries, preview data, analyze column quality, and explore DBA diagnostics — with the official Teradata MCP server supporting optional ML tool expansion via the teradataml Python package. Open dossier | Android Skills MCP Server for Claude Access AI-optimized Android development guides from Claude — search and retrieve SKILL.md content covering Jetpack Compose, Navigation 3, CameraX, AGP 9, App Functions, Edge-to-Edge, Android Profilers, XR, Google Play, and the Android CLI — with the Android Skills MCP server. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Appwrite | jparkerweb | Teradata | Jaewoong Eum (skydoves) |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓Mutation operations (write, update, delete) require `confirm_write=true` to be passed explicitly, adding a confirmation step before any destructive action. The API key scope determines what operations are available — use least-privilege scopes for your use case. | ✓The `query` tool executes arbitrary SQL including INSERT, UPDATE, and DELETE statements — it is not read-only. Point the server at a copy or test database to avoid accidental data loss before trusting it with production data. | ✓The `base_query` tool executes arbitrary SQL on your Teradata system — only connect with credentials scoped to the minimum required permissions. Row limits (`DEFAULT_ROW_LIMIT`, `MAX_ROW_LIMIT`) prevent accidental full-table scans returning millions of rows; leave defaults in place unless you need larger result sets. | ✓The server runs entirely offline — no network requests are made during queries. All skill content is bundled with the npm package. |
| Privacy notes | ✓User records, database documents, function logs, team memberships, and messaging data from your Appwrite project are surfaced in Claude's context. Your `APPWRITE_API_KEY` grants project-level access — keep it in the MCP config env and never commit it to version control. | ✓All database content including table schemas, record data, and query results are surfaced in Claude's context — do not connect databases containing sensitive personal or credential data unless you intend to share it with the model. No credentials are required and no data is sent to external services — the server operates entirely locally. | ✓Query results, schema definitions, DDL, and session/system metadata from your Teradata instance are surfaced in Claude's context. Your database credentials are embedded in the `DATABASE_URI` — keep it in the MCP config env and never commit it to version control. | ✓No API keys, user data, or query content is sent to any external service. All lookups happen locally against the bundled skill snapshot. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.