Mcp For Api

io.github.appwritePublished by GitHub account appwritev0.2.8Updated Oct 24, 2026

MCP (Model Context Protocol) server for Appwrite

VerifiedSTDIODesktop onlyDatabases Cloud & Infrastructure Developer Tools

Server details

Identifier: io.github.appwrite/mcp-for-api
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account appwrite for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.appwrite%2Fmcp-for-api.svg)](https://sourceweft.com/mcp/io.github.appwrite%2Fmcp-for-api?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Exposes Appwrite's backend API — databases, users, functions, teams and storage — as tools an assistant can call, via a hosted OAuth server or a local stdio…

What you can do: Work with Appwrite databases, users, functions, teams and storage through the platform API
List projects and their environments, and pass project and environment IDs on each call
Search Appwrite documentation from an in-process docs tool
Record a short reason with every write so changes appear in the project's audit log
Connect either to the hosted Appwrite Cloud server or, for self-hosted instances, run locally over stdio with a project API key
When to use it: Useful when you build or operate an Appwrite project and want an assistant to inspect or change its data, users, functions, teams or files from inside your MCP client, on Appwrite Cloud or a self-hosted instance.
Requirements: An Appwrite project and account. The hosted server is reached over HTTP and authenticated through a browser OAuth consent screen with scopes you approve; no keys to copy. Clients without OAuth support need Node.js to bridge via npx mcp-remote. Self-hosted instances run the server locally over stdio with a project API key.

Before you install

The agent can write to your Appwrite project — creating or changing data, users, functions, teams and files — under the scopes you approve at consent. Review the requested scopes and the project's Activity audit log. Self-hosted setups require a project API key, which grants broad access to that project. Events/webhook subscriptions are noted as not yet available.

Installation

In SourceWeft

Open Mcp For Api in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Appwrite MCP server

[MCP Registry Version]

A Model Context Protocol server for Appwrite. It exposes Appwrite's API — databases, users, functions, teams, storage, and more — as tools your MCP client can call.

Connect to the hosted server at https://mcp.appwrite.io/ and authenticate through your browser. The first time you connect, your client opens an Appwrite consent screen; approve the scopes and you're connected. There are no keys to copy. The conventional https://mcp.appwrite.io/mcp URL is also supported and connects to the same server.

[How the Appwrite MCP server handles OAuth and scopes]

Connect your client

Pick your client below. Each adds the hosted Appwrite Cloud server.

Claude Code

Then, inside a Claude Code session, run /mcp, select appwrite, and follow the browser prompt to authenticate.

Claude Desktop

Go to Settings → Connectors → Add custom connector and paste https://mcp.appwrite.io/. Available on Pro and Max plans; on Team and Enterprise plans only an organization Owner can add custom connectors.

If you don't see that option (free plan, or a Team/Enterprise member), bridge the remote server through stdio instead (requires Node.js). Go to Settings → Developer → Local MCP servers, click Edit Config, and add:

json

{  "mcpServers": {    "appwrite": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]    }  }}

{  "mcpServers": {    "appwrite": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]    }  }}

Restart Claude Desktop; the server appears under Local MCP servers and a browser window opens to authenticate.

[Appwrite server running under Local MCP servers in Claude Desktop]

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).

Cursor prompts you to log in through the browser; the server then shows up under Settings → MCP with its tools enabled.

[Appwrite server connected in Cursor's MCP settings]

VS Code (GitHub Copilot)

Edit .vscode/mcp.json (workspace) or your user configuration via the Command Palette → MCP: Open User Configuration.

json

{  "servers": {    "appwrite": {      "type": "http",      "url": "https://mcp.appwrite.io/"    }  }}

{  "servers": {    "appwrite": {      "type": "http",      "url": "https://mcp.appwrite.io/"    }  }}

Codex

Edit ~/.codex/config.toml.

Then authenticate from the terminal:

In the Codex GUI, you can instead add the server from the MCP settings — set the URL to https://mcp.appwrite.io/ and leave the token and header fields empty (authentication happens through the browser):

[Appwrite MCP server settings in the Codex GUI]

OpenCode

Edit opencode.json (project) or ~/.config/opencode/opencode.json (global).

json

{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "appwrite": {      "type": "remote",      "url": "https://mcp.appwrite.io/",      "enabled": true    }  }}

{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "appwrite": {      "type": "remote",      "url": "https://mcp.appwrite.io/",      "enabled": true    }  }}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json.

Gemini CLI

Or edit ~/.gemini/settings.json (note the key is httpUrl, not url):

Gemini CLI opens the browser OAuth flow automatically on first connect. To re-authenticate, run /mcp auth appwrite inside a session.

Antigravity (CLI & 2.0)

Edit ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (project workspace).

⚠️ Note: Antigravity strictly requires the serverUrl key for remote transport. Using legacy fields like url or httpUrl will cause tool registration to fail silently.

Antigravity opens the browser OAuth flow automatically on first connect. If you manually edit the JSON file, navigate to Settings → Customizations → Installed MCP Servers and click Refresh to reload the tool definitions.

GitHub Copilot CLI

Or run /mcp add inside a session, or edit ~/.copilot/mcp-config.json:

json

{  "mcpServers": {    "appwrite": {      "type": "http",      "url": "https://mcp.appwrite.io/"    }  }}

{  "mcpServers": {    "appwrite": {      "type": "http",      "url": "https://mcp.appwrite.io/"    }  }}

A browser window opens to authenticate on first connect. Check status with /mcp.

Zed

Go to Settings → AI → MCP Servers → Add Server → Add Remote Server, or add to your settings.json (zed: open settings):

Zed prompts you to authenticate through the browser on first connect.

Warp

Go to Settings → Agents → MCP servers → + Add, choose the URL-based server type, and enter https://mcp.appwrite.io/.

Warp opens a browser window to authenticate on first connect.

JetBrains AI Assistant / Junie

JetBrains IDEs don't yet support OAuth for remote MCP servers, so bridge through stdio (requires Node.js). Go to Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add, switch to the JSON view, and paste:

json

{  "mcpServers": {    "appwrite": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]    }  }}

{  "mcpServers": {    "appwrite": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]    }  }}

A browser window opens to authenticate on first connect.

Cline

Cline doesn't yet support OAuth for remote MCP servers, so bridge through stdio (requires Node.js). In the Cline panel, open the MCP Servers icon → Configure tab → Configure MCP Servers, and add:

json

{  "mcpServers": {    "appwrite": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]    }  }}

{  "mcpServers": {    "appwrite": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.appwrite.io/"]    }  }}

A browser window opens to authenticate on first connect.

Reasons and environments

Every write the agent makes carries a short reason (why it made the change). Appwrite records it on the project's audit log, so you can review what your agent changed, and why, in the project's Activity tab.

On Appwrite Cloud, the agent can act in a project's environments (for example staging): appwrite_get_context lists them, and each call takes the environment's ID as environment_id next to the project's project_id. See Tool surface.

Self-hosted Appwrite

Running your own Appwrite instance? Run the MCP server locally over stdio and authenticate with a project API key. See docs/self-hosted.md for per-client setup.

Documentation

Tool surface — the tools exposed to the model and the internal Appwrite catalog.
How Cloud authentication works — the OAuth 2.1 flow.
Documentation search — the in-process appwrite_search_docs tool and how to rebuild its index.
Events — MCP Events: webhook subscriptions to changes in your Appwrite project (in development, not available yet).
Self-hosted Appwrite — run the server locally with a project API key.
Local development — running, testing, and debugging the server locally.
AGENTS.md — full contributor guide and pre-PR checklist.

License

This MCP server is licensed under the MIT License. See the LICENSE file for details.

Source: README.md at commit 57d61ab

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.8LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts