Developer · Remote MCP server
appwrite MCP
Manage Appwrite projects, databases, auth, storage, functions, and messaging; search Appwrite docs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.appwrite/mcp- Version
- 1.0.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- PyPI
- Published
- 2026-10-02
- Updated
- 2026-10-02
- Publisher
- appwrite (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/appwrite) · how
- Repository
- github.com/appwrite/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.appwrite.io/ | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | mcp-server-appwrite | 1.0.2 | stdio |
How to connect appwrite MCP
appwrite MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.appwrite.io/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Python package published to PyPI: mcp-server-appwrite version 1.0.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx mcp-server-appwrite.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "uvx",
"args": [
"mcp-server-appwrite"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| AppsignalMCP server for AppSignal - get alert details, search logs, and retrieve logs within time ranges. | Local · stdio |
| Appstoreconnect MCPApp Store Connect for MCP clients: PPP pricing, subscriptions, TestFlight, reviews, reports & more. | Local · stdio |
| Appveyor MCPCI pipeline monitoring for GitLab and GitHub - no API key. | Local · stdio |
| AppWizzy ProjectsCreate and monitor AppWizzy app environments from GitHub or ZIP with AI agents. | Remote · HTTPLive check: sign-in required |
| ApricotManage SysML2 projects and files directly through your coding agent. | Remote · HTTPLive check: sign-in required |
| Aptu CoderMCP server for code structure analysis using tree-sitter. | Local · stdio |
| ApuchatReal-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP. | Remote · HTTPLive check: ✓ handshake |
| Arbeitsvertrag Nachwg LintArbeitsvertrag-Vorlagen gegen das Nachweisgesetz prüfen: 15 Pflichtangaben seit 1. August 2022 (§2 N. | Local · stdio |