M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
A

Appwrite MCP Server

Official
Operate your Appwrite backend through your MCP client.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #74 of 438
Stars
★ 72 Popular
Transport
Streamable HTTP · stdio (local process)
Runtime
Hosted (no local runtime)
Credentials
API key / credential required
License
MIT
Last commit
Tools
1
63FMRS · C

An official, Appwrite-maintained MCP server that lets many MCP clients manage Appwrite databases, users, functions, teams, and storage via a hosted OAuth endpoint or a self-hosted stdio option.

Strongest · Documentation 16/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
12/20
Maintenance
13/20
Documentation
16/20
Setup experience
14/20
Why each score
Reliability 8/20
The README documents multiple connection paths (hosted OAuth, npx mcp-remote bridging, local stdio self-hosting) and links out to docs/tool-surface.md and others, indicating the tool surface is documented, but no server manifest was available (marked 'not cached') and no CI workflow files or committed tests were provided as verifiable execution evidence. Per the static calibration rule, reliability is capped at 12 without real CI plus tests covering key paths. Since there is no way to confirm declared tools match actual behavior or how errors/dependencies are controlled, this is judged as 'plausible happy path but thin evidence,' scoring 8.
Security and permissions 12/20
The hosted service uses an OAuth 2.1 browser flow with explicit scope approval and no plaintext keys appear in setup examples; the self-hosted mode uses a project API key, a standard practice not exposed with real secrets in the docs — no red line is triggered. However, the Appwrite MCP server exposes backend operations across databases, users, functions, and storage, and the README gives no detail on confirmation steps or least-privilege scoping for potentially destructive actions (e.g., delete, deploy), and no tool-level permission manifest was available to verify. This evidence gap caps the score at a moderate 12 rather than higher.
Maintenance 13/20
The repo is MIT-licensed, not archived, has 71 stars and 4 open issues, and the README displays an MCP Registry version badge indicating an active publishing/versioning pipeline. However, no commit history, release cadence, issue-response times, or dependency-update policy were provided as evidence, so activity level cannot be fully confirmed, yielding a moderate 13.
Documentation 16/20
Documentation is well-layered: the README provides concrete configuration snippets for over a dozen mainstream clients (Claude Code, Claude Desktop, Cursor, VS Code, Codex, OpenCode, Windsurf, Gemini CLI, Antigravity, GitHub Copilot CLI, Zed, Warp, JetBrains, Cline) and links to separate docs for tool surface, authentication, documentation search, self-hosting, local development, and contributor guidelines. However, detailed tool parameters, limits, cost, and troubleshooting content are not directly included in the provided material and can only be inferred to exist via external links, so it falls short of full marks at 16.
Setup experience 14/20
For the hosted server, setup is streamlined — most clients need only a short config block or single command, with browser-based OAuth removing the need to manage keys; self-hosting is also separately documented. Per the static calibration rule, setup cannot exceed 15 without verifiable execution evidence (real CI plus tests covering key paths), and the absence of a cached manifest means the described setup steps could not be independently verified, resulting in a score of 14.

Static review · not runListed 2026-08-26

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkConnects to a database

Best for

  • Developers already on Appwrite Cloud who want AI-assisted backend administration
  • Teams that prefer browser-authenticated OAuth scopes over managing API keys
  • Self-hosted Appwrite operators who can run a local stdio bridge with a project API key

Not for

  • Users without an Appwrite project or account
  • Clients that lack remote MCP/OAuth support and cannot install Node.js for the mcp-remote bridge
  • Non-Appwrite backend workflows

Required permissions

  • OAuth scopes approved during the browser consent flow (covering databases, users, functions, teams, storage, etc.)
  • For self-hosted use, an Appwrite project API key with permissions matching the operations invoked

Risks and side effects

  • Broad backend access (databases, users, functions, storage) if overly broad OAuth scopes or an overly permissive API key are granted
  • Destructive operations (deleting data, modifying users/teams) are possible if the AI client is given write scopes
  • The hosted server is a third-party (Appwrite-operated) service brokering requests to your Appwrite project

Setup

Before you start

Runtime：Hosted (no local runtime)

Add the hosted endpoint https://mcp.appwrite.io/ (the /mcp path also works) as a remote/HTTP MCP server in a supporting client, then approve the Appwrite OAuth consent screen in your browser on first connect — no keys to copy. Clients without native remote-MCP/OAuth support (e.g., JetBrains, Cline) can bridge it over stdio with npx -y mcp-remote https://mcp.appwrite.io/. For self-hosted Appwrite, run the server locally over stdio and authenticate with a project API key (see docs/self-hosted.md).

.mcp.json 
{"mcpServers":{"appwrite":{"url":"https://mcp.appwrite.io/"}}}

Shown for Claude Code. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "appwrite": {
      "url": "https://mcp.appwrite.io/"
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add --transport http appwrite https://mcp.appwrite.io/

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Connect to https://mcp.appwrite.io/ and complete the browser OAuth consent; appwrite_search_docs should appear in the client's tool list. Ask it to search the Appwrite docs for 'databases' — a returned result proves the connection works.

Troubleshooting

  1. Confirm the client supports remote/HTTP MCP servers and OAuth; otherwise use the mcp-remote stdio bridge
  2. Re-run the browser authentication flow if the consent screen doesn't appear or the connection fails
  3. On Claude Desktop Team/Enterprise plans, only an organization Owner can add custom connectors
  4. For self-hosted setups, verify the project API key and check docs/self-hosted.md for per-client configuration
  5. Check docs/tool-surface.md for the exact tools exposed if a call is unavailable

Things to try

Once connected, you can ask your AI assistant things like:

  • Use appwrite_search_docs to look up how to create an Appwrite database collection
  • Search the Appwrite docs for how storage works
  • Find in the Appwrite documentation how to deploy functions

Tools 1

appwrite_search_docs read-only
An in-process tool for searching Appwrite documentation to answer questions about the platform's APIs and features.

Use cases

Managing Appwrite databases, collections, and documents from an AI assistant
Creating and inspecting Appwrite users and teams via natural language
Deploying and managing Appwrite functions
Searching Appwrite documentation in-process
Automating Appwrite storage/bucket operations

Supported clients

Claude Code
Claude Desktop
Cursor
VS Code
Codex
OpenCode
Windsurf
Gemini CLI
Antigravity
GitHub Copilot CLI
Zed
Warp
JetBrains AI Assistant / JuniePartial support
ClinePartial support

Listed from the project's documentation, not tested by this site.

Overview

The official Model Context Protocol server for Appwrite, exposing its API — databases, users, functions, teams, storage, and more — as callable tools. Connect to a hosted, browser-authenticated OAuth endpoint, or run it locally over stdio against a self-hosted Appwrite instance using a project API key.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 32616df5c5cf Data synced 2026-10-12 Read the FMRS scoring method