home / mcp / appwrite docs mcp server
Provides up-to-date Appwrite documentation through MCP endpoints for IDEs and copilots.
Configuration
View docs{
"mcpServers": {
"appwrite-mcp-for-docs": {
"url": "https://mcp-for-docs.appwrite.io"
}
}
}You can run the Appwrite Docs MCP Server to expose Appwrite’s documentation as a source of truth for your IDEs. This server lets your code editor or assistant fetch up-to-date docs, navigate topics, and reference guidance directly from your development environment.
You connect to the MCP server from your MCP client (Cursor, Windsurf, Claude Code, VSCode, or another compatible client) by adding the server as an MCP endpoint. The server provides an HTTP endpoint for remote access and a local stdio flow for development and testing.
Prerequisites: ensure you have Bun installed on your machine to run the MCP server locally.
Install dependencies for the MCP server locally.
Run the following commands to set up and start the MCP server locally.
bun install
bun run init
bun run build
bun run startConfiguration, security, and usage notes are described below to help you operate the server smoothly.
You can connect via an HTTP MCP endpoint or via local stdio for development.
# HTTP configuration (remote MCP URL)
{
"type": "http",
"name": "appwrite_docs_mcp",
"url": "https://mcp-for-docs.appwrite.io",
"args": []
}# STDIO configuration (local runtime)
{
"type": "stdio",
"name": "appwrite_docs_mcp",
"command": "bun",
"args": ["run", "start"]
}Set up the server by downloading content to ./content and generating the table of contents, then initialize the vector store with documentation and metadata.
Compile the MCP server code so it can run in production or locally with bun run build.
Launch the MCP server so it is accessible at http://localhost:1234 by default.
Open an inspector UI in your browser to examine the MCP server and its configuration.