Log inSubmit server
Appwrite MCP logo

Appwrite MCP

by appwrite

Connects MCP clients to Appwrite for managing databases, users, functions, teams, storage, messaging, and other API resources.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Appwrite MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.appwrite.io/

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 1d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 1d ago · Nov 12, 2026, 22:45 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.appwrite.io/

Overview

appwrite/mcp MCP server exposes Appwrite API operations as tools that MCP-compatible clients can call. The hosted endpoint at https://mcp.appwrite.io/ uses browser-based OAuth, so hosted connections do not require copying API keys. Developers running their own Appwrite instance can self-host the server over stdio with a project API key. Reach for it when an AI agent needs to inspect or manage Appwrite project resources from a supported MCP client.

Use cases

  • Manage Appwrite databases through an AI client
  • Administer Appwrite users and authentication resources
  • Inspect and operate Appwrite functions
  • Work with Appwrite teams, storage, and messaging
  • Search Appwrite documentation from an MCP session

Key features

  • Hosted Appwrite connection over HTTP
  • Browser-based OAuth without copied API keys
  • Self-hosted stdio mode with a project API key
  • Tools for databases, users, functions, teams, storage, and messaging
  • In-process Appwrite documentation search

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

26/26 checks healthy over the last 95d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars72Stargazers on the source repository.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Appwrite MCP works

What appwrite/mcp does

appwrite/mcp exposes Appwrite functionality through the Model Context Protocol. Its tool surface covers Appwrite services including databases, users, functions, teams, storage, messaging, authentication, and other API resources. This lets an MCP client present Appwrite operations to an AI agent without requiring the agent to use Appwrite's HTTP API directly.

The server is suitable for tasks that involve managing Appwrite project resources through an AI-assisted development workflow. Access is controlled through the selected authentication method and the scopes granted during authorization.

How it works

The hosted service is available at https://mcp.appwrite.io/. The conventional /mcp path is also supported and points to the same service. Remote clients connect over HTTP and begin an OAuth flow in the browser. During the first connection, Appwrite displays a consent screen where the user approves the requested scopes; no API key needs to be copied into the client configuration.

For a self-managed Appwrite installation, the server can run locally over stdio. That mode authenticates with a project API key and is intended for connections to an instance you operate yourself.

Setup and configuration

For hosted use, add https://mcp.appwrite.io/ as a remote MCP server in a compatible client, then complete the browser authentication prompt. Clients with documented connection procedures include Claude Code, Claude Desktop, Cursor, VS Code with GitHub Copilot, Codex, Windsurf, Gemini CLI, Zed, JetBrains AI Assistant or Junie, and Cline.

Claude Desktop and JetBrains AI Assistant or Junie can use the hosted service through an mcp-remote stdio bridge when direct remote OAuth is unavailable. Cline likewise uses that bridge and requires Node.js. Codex can authenticate from the terminal with codex mcp login appwrite, while Gemini CLI supports reauthentication through /mcp auth appwrite.

Self-hosted deployments require a local server process and a project API key. Client-specific self-hosting instructions are provided by the project.

Tools and capabilities

The exposed Appwrite API surface includes operations for:

  • Databases
  • Authentication and users
  • Functions
  • Teams
  • Storage
  • Messaging
  • Other Appwrite services and resources

The project also documents an in-process appwrite_search_docs tool for searching Appwrite documentation.

Limitations and notes

Hosted OAuth support varies by client. JetBrains AI Assistant or Junie and Cline do not support OAuth for remote MCP servers directly, so they require the stdio bridge. Claude Desktop may require a supported plan or organization permissions for custom remote connectors.

MCP Events, described as webhook subscriptions for project changes, are still in development and are not available. The hosted service and self-hosted mode use different authentication approaches: browser OAuth for the former and a project API key for the latter.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Appwrite MCP

appwrite/mcp is an MCP server that connects AI clients to Appwrite through hosted OAuth or a self-hosted stdio process. Its tools expose Appwrite capabilities for databases, authentication, users, functions, teams, storage, messaging, and documentation search, allowing agents to work with project resources through the Model Context Protocol.

Add `https://mcp.appwrite.io/` as a remote MCP server in a supported client and complete the browser OAuth flow. For self-hosted Appwrite, run the server locally over stdio and authenticate with a project API key. Some clients require an `mcp-remote` bridge and Node.js.

Yes, appwrite/mcp works with Cursor through its remote MCP configuration. Add an `appwrite` server with the URL `https://mcp.appwrite.io/` in the global or project `mcp.json` file, then authenticate in the browser when Cursor prompts you.

Yes, appwrite/mcp works with Claude Desktop as a custom remote connector when that option is available. Otherwise, configure Claude Desktop to run `npx -y mcp-remote https://mcp.appwrite.io/` as a local MCP server; Node.js is required for the bridge.

Yes, appwrite/mcp supports self-hosted Appwrite through a local stdio process authenticated with a project API key. The hosted OAuth endpoint is intended for the Appwrite Cloud connection, while self-hosted deployments use client-specific local setup instructions.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAppwrite MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/appwrite-mcp?style=directory)](https://allmcps.com/mcp/appwrite-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/appwrite-mcp"><img src="https://allmcps.com/api/badge/appwrite-mcp?style=directory" alt="Appwrite MCP on AllMCPs" /></a>