diff --git a/.optimize-cache.json b/.optimize-cache.json index b68b74a2a4..d637bd84d8 100644 --- a/.optimize-cache.json +++ b/.optimize-cache.json @@ -243,6 +243,7 @@ "static/images/blog/announcing-realtime-channel-helpers/cover.png": "cbcffde3edfb77908566ff6361cb31bb1175d64bb1958a038720c52748dfa904", "static/images/blog/announcing-realtime-queries/cover.png": "2e11ad5d30399bced1817ce0edb6d266cc57a70955d2102af173d26461c9bf57", "static/images/blog/announcing-relationship-queries/cover.png": "7e615c0a9dcbb3949d5fb7ed71f36bb44de40ae67c8cd832b96ff5bbd4b0f451", + "static/images/blog/announcing-remote-appwrite-mcp-server/cover.png": "f833c55d6fdad8e6ac24de32998dc9c36945d44dd9c5c665dbc189e3afbeea9e", "static/images/blog/announcing-rust-runtime/cover.png": "a203fe2ef16c40592813ae7efb3c746d4250e68414c9b7d763893dae264f61d7", "static/images/blog/announcing-screenshots-api/cover.png": "56555006946b9ead5cd4258544b6a9dda44bce6841706749f7539bc31356383e", "static/images/blog/announcing-self-serve-baa.png": "b66eb0be9b323fb4b28f16218887a463bd1d45f7838c08d6d49e4822a6f95609", @@ -1383,6 +1384,7 @@ "static/images/changelog/2026-04-08.png": "ad7549efc81af619c7bb1429472d3e792d9e49fd6be8e831027ad64c8da8a260", "static/images/changelog/2026-04-21.png": "4134ae96f05ac2a603272582d68a2cfad5af0a804d19c414db709ca80e817cfb", "static/images/changelog/2026-05-05.png": "26c94f354ac186bdb999e31ea1c33a9b5a7bf6312bd30a737da134456330299a", + "static/images/changelog/2026-07-31.png": "f833c55d6fdad8e6ac24de32998dc9c36945d44dd9c5c665dbc189e3afbeea9e", "static/images/changelog/oss-progam.png": "e50d1c497ac1d07494fa1d40b1f219c8f14770f7b72e1258147f527e86f40eed", "static/images/changelog/threads-cover.png": "f5599b528f33797f125da1fecaffc70763118d4d420b04f6d67a70bc651cf40a", "static/images/community/avatars/1.png": "3448e87720fd3f55326ad04f18263f5094b61116c79d7e48e8b692b8012513bc", @@ -1513,10 +1515,10 @@ "static/images/docs/mcp/antigravity/agent-chat.png": "6becbb28e94198cc93e2446df90384b627c00cab8c18772d84f0f728e6fb3c8e", "static/images/docs/mcp/appwrite/appwrite-api-secret.png": "580f1fef314f8eaeee0df5fb4a6af988fe0c381aa5f29aeb3d4b311553ac2370", "static/images/docs/mcp/appwrite/dark/appwrite-api-secret.png": "424649c12773641f5f7d9c779c6d5be3c20c138a325ee930080c718032aaf512", - "static/images/docs/mcp/bolt/bolt-add-mcp.png": "20d897c74e8cf8fa2ef8d4a13a8bae71b2d6fa4ddc8f72f9c6f58279d5dba0a2", - "static/images/docs/mcp/bolt/bolt-mcp-settings.png": "cf29fc3f9490047eef9758f5c5d24f75148e40fa40bd05de8e6df754a5eae384", - "static/images/docs/mcp/bolt/light/bolt-add-mcp.png": "1b6a5910cf3ff34f239acc03221042101979a8688bccde47f25aba87751c7c7e", - "static/images/docs/mcp/bolt/light/bolt-mcp-settings.png": "1dea0c117e29421a7d32966923bdfbba7dfb8d8bcc825a813329c2ac8d0fc1c3", + "static/images/docs/mcp/bolt/bolt-add-mcp.png": "9e8e1b1175164621272118a1d63a00d7a4a4587ca808d1d35ae8eaee630de9a4", + "static/images/docs/mcp/bolt/bolt-mcp-settings.png": "c3f7f09862402b39f69646d6f58584717eaa468f78d4336cfcd2b3dbf11366f1", + "static/images/docs/mcp/bolt/light/bolt-add-mcp.png": "4de5f728b757345bb4186ff168fee32f15885d019f38a1da6e691bd64fceaf9c", + "static/images/docs/mcp/bolt/light/bolt-mcp-settings.png": "ffc79acf9be54d9ddda2e7c734812571339c90c87cfb3820a93e46c80d4607ca", "static/images/docs/mcp/claude-code/configure-plugin.png": "6f089ec25a250408dec84e2986681237d29c7ac382740857f155db20b60cc7d8", "static/images/docs/mcp/claude-code/implement-file-uploads.png": "6e8e6d9b49d5d74d2774ddb332323de608ad0e9ebbef2fdbf3e43644af5cc55a", "static/images/docs/mcp/claude-code/verify-mcp-tools.png": "7dad588fb8a57e767b4bff323169bc7d99c385232cb6f13eda659e9b722c2984", diff --git a/src/partials/mcp-add-ides-tools.md b/src/partials/mcp-add-ides-tools.md index 70e2de64de..12cf22923d 100644 --- a/src/partials/mcp-add-ides-tools.md +++ b/src/partials/mcp-add-ides-tools.md @@ -30,6 +30,9 @@ You can add the MCP server to various AI tools and code editors: {% cards_item href="/docs/tooling/ai/agents/antigravity" title="Google Antigravity" image="/images/docs/mcp/logos/google-antigravity.svg" %} {% /cards_item %} +{% cards_item href="/docs/tooling/ai/agents/grok-build" title="Grok Build" image="/images/docs/mcp/logos/grok-build.svg" %} +{% /cards_item %} + {% /cards %} {% /only_light %} @@ -63,6 +66,9 @@ You can add the MCP server to various AI tools and code editors: {% cards_item href="/docs/tooling/ai/agents/antigravity" title="Google Antigravity" image="/images/docs/mcp/logos/dark/google-antigravity.svg" %} {% /cards_item %} +{% cards_item href="/docs/tooling/ai/agents/grok-build" title="Grok Build" image="/images/docs/mcp/logos/dark/grok-build.svg" %} +{% /cards_item %} + {% /cards %} {% /only_dark %} diff --git a/src/routes/blog/post/announcing-appwrite-claude-code-plugin/+page.markdoc b/src/routes/blog/post/announcing-appwrite-claude-code-plugin/+page.markdoc index dddeaddc98..93345ad11f 100644 --- a/src/routes/blog/post/announcing-appwrite-claude-code-plugin/+page.markdoc +++ b/src/routes/blog/post/announcing-appwrite-claude-code-plugin/+page.markdoc @@ -3,6 +3,7 @@ layout: post title: "Introducing the Appwrite plugin for Claude Code: Skills and MCP servers in one install" description: The Appwrite plugin for Claude Code bundles agent skills and MCP servers into a single install, so your Claude Code agent can build with Appwrite out of the box. date: 2026-04-20 +lastUpdated: 2026-07-31 cover: /images/blog/announcing-appwrite-claude-code-plugin/cover.avif timeToRead: 4 author: atharva @@ -23,6 +24,12 @@ faqs: answer: "Check the [Appwrite Skills documentation](/docs/tooling/ai/skills), which explains what skills are, how the AI agent loads them, and how to use them with other AI tools beyond Claude Code. The plugin bundles eleven of these skills out of the box." --- +{% info title="Update (July 2026)" %} + +The Appwrite MCP server is now a hosted remote server at `https://mcp.appwrite.io/` that uses OAuth authentication, with documentation search built in. The API-key configuration described in this post is no longer needed for Appwrite Cloud, and the plugin is being updated to accommodate the same changes. Read the [changelog entry](/changelog/entry/2026-07-31) for details. + +{% /info %} + Claude Code is built around a specific workflow: a terminal-resident agent that reads, writes, and runs code against your project. Using it with Appwrite has worked for a while, but getting there meant hand-registering MCP servers with `claude mcp add-json`, pasting your project credentials into a JSON payload, and relying on whatever SDK knowledge the underlying model was trained on. Today, we are announcing the **Appwrite plugin for Claude Code**. Two commands and your agent is set up to build with Appwrite using up-to-date SDK patterns and live access to your project. diff --git a/src/routes/blog/post/announcing-appwrite-codex-plugin/+page.markdoc b/src/routes/blog/post/announcing-appwrite-codex-plugin/+page.markdoc index 11c72ca3d8..06f697f66b 100644 --- a/src/routes/blog/post/announcing-appwrite-codex-plugin/+page.markdoc +++ b/src/routes/blog/post/announcing-appwrite-codex-plugin/+page.markdoc @@ -3,6 +3,7 @@ layout: post title: "Introducing the Appwrite plugin for Codex: Skills and MCP in one install" description: The Appwrite plugin for Codex bundles agent skills and the Appwrite Docs MCP server into a single install, so Codex can build with Appwrite out of the box. date: 2026-05-11 +lastUpdated: 2026-07-31 cover: /images/blog/announcing-appwrite-codex-plugin/cover.avif timeToRead: 4 author: aditya-oberai @@ -23,6 +24,12 @@ faqs: answer: "No. The plugin bundles the same [Appwrite language and CLI skills](/docs/tooling/ai/skills), so installing the plugin gives Codex everything it needs in one step. You only need to install skills separately if you want to use them with another [AI IDE, CLI, or dev tool](/docs/tooling/ai) that doesn't have its own Appwrite plugin yet." --- +{% info title="Update (July 2026)" %} + +The Appwrite MCP server is now a hosted remote server at `https://mcp.appwrite.io/` that uses OAuth authentication, with documentation search built in. The API-key configuration described in this post is no longer needed for Appwrite Cloud, and the plugin is being updated to accommodate the same changes. Read the [changelog entry](/changelog/entry/2026-07-31) for details. + +{% /info %} + Codex is OpenAI's terminal-resident coding agent. It reads, writes, and runs code against your project, and it has been steadily picking up the building blocks needed to work well with platforms like Appwrite: skills for language-specific context, MCP servers for live tool and documentation access, and a marketplace for distributing them. Using Codex with Appwrite has worked for a while, but getting set up meant copying skill files into `~/.codex/skills/`, hand-editing `~/.codex/config.toml` to register the docs MCP, and stitching everything together yourself. Today, we are announcing the **Appwrite plugin for Codex**. Add the marketplace, install the plugin, and your agent is ready to build with Appwrite using up-to-date SDK patterns and live access to the Appwrite documentation. diff --git a/src/routes/blog/post/announcing-appwrite-cursor-plugin/+page.markdoc b/src/routes/blog/post/announcing-appwrite-cursor-plugin/+page.markdoc index ab13680419..5e91942c9e 100644 --- a/src/routes/blog/post/announcing-appwrite-cursor-plugin/+page.markdoc +++ b/src/routes/blog/post/announcing-appwrite-cursor-plugin/+page.markdoc @@ -3,6 +3,7 @@ layout: post title: "Introducing the Appwrite plugin for Cursor: Skills, MCP, and commands in one install" description: The Appwrite plugin for Cursor bundles agent skills, MCP servers, and deployment commands into a single install, so your AI agents can build with Appwrite out of the box. date: 2026-04-06 +lastUpdated: 2026-07-31 cover: /images/blog/announcing-appwrite-cursor-plugin/cover.avif timeToRead: 4 author: atharva @@ -23,6 +24,12 @@ faqs: answer: "MCP servers give the agent runtime access to your Appwrite project so it can create users, query databases, or read docs on demand. Skills give the agent static, curated knowledge about how to write Appwrite code correctly. The plugin includes both because agents need accurate context for code generation and live access for project operations." --- +{% info title="Update (July 2026)" %} + +The Appwrite MCP server is now a hosted remote server at `https://mcp.appwrite.io/` that uses OAuth authentication, with documentation search built in. The API-key configuration described in this post is no longer needed for Appwrite Cloud, and the plugin is being updated to accommodate the same changes. Read the [changelog entry](/changelog/entry/2026-07-31) for details. + +{% /info %} + Earlier this year, we launched [Appwrite Skills](/docs/tooling/ai/skills), open-source Markdown files that give AI agents deep, language-specific knowledge of Appwrite SDKs. Skills solved a real problem: agents were generating Appwrite code that looked right but used the wrong method signatures, outdated patterns, or missing parameters. With skills installed, agents generate correct, idiomatic Appwrite code without needing documentation pasted into every prompt. Today, we are taking a step further. diff --git a/src/routes/blog/post/announcing-appwrite-mcp-server-2/+page.markdoc b/src/routes/blog/post/announcing-appwrite-mcp-server-2/+page.markdoc index 6d884ffb3e..b0ae6b5133 100644 --- a/src/routes/blog/post/announcing-appwrite-mcp-server-2/+page.markdoc +++ b/src/routes/blog/post/announcing-appwrite-mcp-server-2/+page.markdoc @@ -3,6 +3,7 @@ layout: post title: "Announcing Appwrite MCP Server 2.0" description: The Appwrite MCP server has been rebuilt with a compact two-tool architecture that uses less context, requires zero configuration flags, and automatically supports all Appwrite services. date: 2026-04-13 +lastUpdated: 2026-07-31 cover: /images/blog/announcing-appwrite-mcp-server-2/cover.avif timeToRead: 4 author: chirag-aggarwal @@ -23,6 +24,12 @@ faqs: answer: "Yes. The MCP server accepts the same connection settings as the Appwrite SDKs (endpoint, project ID, API key), so you can point it at a self-hosted Appwrite instance. The [MCP server documentation](/docs/tooling/ai/mcp-servers/api) walks through configuration for both Cloud and self-hosted setups." --- +{% info title="Update (July 2026)" %} + +The Appwrite MCP server is now a hosted remote server at `https://mcp.appwrite.io/` that uses OAuth authentication, with documentation search built in. It replaces the local setup described in this post for Appwrite Cloud users. Read the [changelog entry](/changelog/entry/2026-07-31) for details. + +{% /info %} + When we launched the Appwrite MCP server, connecting your Appwrite project to AI coding agents was already straightforward. But as the number of enabled services grew, so did the number of tool definitions loaded into the model's context, leaving less room for your actual prompts and code. Today, we are releasing Appwrite MCP Server 2.0, a ground-up rethink of how the server exposes Appwrite's capabilities to AI models. diff --git a/src/routes/blog/post/announcing-remote-appwrite-mcp-server/+page.markdoc b/src/routes/blog/post/announcing-remote-appwrite-mcp-server/+page.markdoc new file mode 100644 index 0000000000..3564ab4652 --- /dev/null +++ b/src/routes/blog/post/announcing-remote-appwrite-mcp-server/+page.markdoc @@ -0,0 +1,126 @@ +--- +layout: post +title: "The Appwrite MCP server is now remote: one URL, no API keys" +description: The Appwrite MCP server is now a hosted remote server. Add one URL to your AI tool, sign in with OAuth, and start building. No installs, no API keys, nothing to keep updated. +date: 2026-07-31 +cover: /images/blog/announcing-remote-appwrite-mcp-server/cover.avif +timeToRead: 4 +author: aditya-oberai +category: product, announcement +featured: false +faqs: + - question: "What is the remote Appwrite MCP server?" + answer: "It is a hosted version of the [Appwrite MCP server](/docs/tooling/ai/mcp-servers/api) that runs over the HTTP transport at `https://mcp.appwrite.io/`. Instead of installing and running the server locally, you add the URL to your AI tool's MCP configuration and authenticate with OAuth. It gives AI agents like Claude Code, Cursor, and Codex access to your Appwrite project and the Appwrite documentation." + - question: "How does authentication work without an API key?" + answer: "The remote server uses OAuth. The first time your AI tool connects, your browser opens so you can sign in to your Appwrite account and authorize access. There are no API keys to create, scope, paste into config files, or rotate." + - question: "Do I still need uv or Python installed?" + answer: "Not for Appwrite Cloud. The remote server is hosted by Appwrite, so there is nothing to install or keep updated on your machine. The local setup with [uv](https://docs.astral.sh/uv/getting-started/installation/) and an API key is still supported and remains the way to connect to [self-hosted Appwrite instances](/docs/tooling/ai/mcp-servers/api#self-hosted)." + - question: "Does the remote server keep the compact architecture from MCP Server 2.0?" + answer: "Yes. The remote server keeps the search-and-call architecture introduced in [MCP Server 2.0](/blog/post/announcing-appwrite-mcp-server-2): `appwrite_search_tools` and `appwrite_call_tool`, now joined by `appwrite_get_context` for workspace context and `appwrite_search_docs` for documentation search. The full Appwrite tool catalog stays internal and is searched at runtime, so the model's context is not filled with tool definitions it may never use." + - question: "Do I still need the separate Appwrite docs MCP server?" + answer: "No. Documentation access is consolidated into the remote Appwrite MCP server through the `appwrite_search_docs` tool, which semantically searches the Appwrite documentation. One connection covers both your Appwrite project and the docs." + - question: "Which AI tools work with the remote Appwrite MCP server?" + answer: "Any MCP client that supports remote servers over the HTTP transport with OAuth, including Claude Code, Codex, Cursor, Claude Desktop, VS Code, Zed, OpenCode, Windsurf, Zenflow, Google Antigravity, and Grok Build. The [documentation](/docs/tooling/ai) has setup guides for each tool." +--- + +The Appwrite MCP server connects AI coding agents to your Appwrite project, so tools like Claude Code, Cursor, and Codex can create users, manage databases, deploy functions, and work with every other Appwrite service from a chat. Until now, using it meant running a server on your own machine: installing uv, creating an API key with the right scopes, and pasting your endpoint, project ID, and key into every tool's MCP configuration. + +Today, we are making that entire setup disappear. The Appwrite MCP server is now available as a **hosted remote server**. Add one URL to your AI tool, sign in with your Appwrite account, and start building: + +``` +https://mcp.appwrite.io/ +``` + +# What changed + +The remote server replaces the local setup for Appwrite Cloud users, and it removes every step that used to sit between you and a working connection: + +- **No local install**: The server runs as a hosted HTTP service. You no longer need uv, Python, or a locally running process, and there is nothing to keep updated. You always get the latest version. +- **No API keys**: The server uses OAuth. The first time your AI tool connects, your browser opens so you can sign in to your Appwrite account and authorize access. No keys to create, scope, share, or rotate. +- **One config line**: Your MCP configuration goes from a command, arguments, and three environment variables down to a single URL. +- **Docs included**: The server also searches the Appwrite documentation through the `appwrite_search_docs` tool, replacing the separate docs MCP server. One connection covers both your project and the docs. + +Here is the difference in a Claude Code `.mcp.json`: + +{% tabs %} +{% tabsitem #after title="After" %} + +```json +{ + "mcpServers": { + "appwrite": { + "type": "http", + "url": "https://mcp.appwrite.io/" + } + } +} +``` + +{% /tabsitem %} + +{% tabsitem #before title="Before" %} + +```json +{ + "mcpServers": { + "appwrite": { + "command": "uvx", + "args": ["mcp-server-appwrite"], + "env": { + "APPWRITE_API_KEY": "your-api-key", + "APPWRITE_PROJECT_ID": "your-project-id", + "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" + } + } + } +} +``` + +{% /tabsitem %} +{% /tabs %} + +{% info title="Self-hosting Appwrite?" %} + +The local setup shown in the **Before** tab is still fully supported. If you run a [self-hosted Appwrite instance](/docs/advanced/self-hosting), the local MCP server continues to work with your API key. See the [self-hosted setup](/docs/tooling/ai/mcp-servers/api#self-hosted) in the documentation. + +{% /info %} + +# Same context-efficient architecture + +The remote server keeps the compact architecture introduced in [MCP Server 2.0](/blog/post/announcing-appwrite-mcp-server-2). Only a small set of MCP tools is exposed to the model: + +- **`appwrite_get_context`**: Returns a summary of your workspace, including your account, organization, and projects. +- **`appwrite_search_tools`**: Searches the full Appwrite tool catalog based on the model's intent. +- **`appwrite_call_tool`**: Executes a specific Appwrite operation by name. +- **`appwrite_search_docs`**: Semantically searches the Appwrite documentation. + +The full catalog of Appwrite operations stays internal to the server and is searched at runtime, so all Appwrite services are available without filling the model's context with unused tool definitions. And because documentation search is built in, the separate Appwrite docs MCP server is no longer needed: one connection covers both your project and the docs. + +# Get started + +Adding the server takes one step in most tools. In Claude Code, for example: + +```bash +claude mcp add --transport http appwrite https://mcp.appwrite.io/ +``` + +Then run `/mcp`, select **appwrite**, and choose **Authenticate** to sign in. + +In Cursor, VS Code, Zed, and other editors, add the URL to your MCP configuration and complete the OAuth sign-in when prompted. The documentation has step-by-step guides for [Claude Code](/docs/tooling/ai/agents/claude-code), [Codex](/docs/tooling/ai/agents/codex), [Cursor](/docs/tooling/ai/agents/cursor), [Claude Desktop](/docs/tooling/ai/vibe-coding/claude-desktop), [VS Code](/docs/tooling/ai/agents/vscode), [Zed](/docs/tooling/ai/agents/zed), [OpenCode](/docs/tooling/ai/agents/opencode), [Windsurf](/docs/tooling/ai/agents/windsurf), [Zenflow](/docs/tooling/ai/vibe-coding/zenflow), [Google Antigravity](/docs/tooling/ai/agents/antigravity), and [Grok Build](/docs/tooling/ai/agents/grok-build). + +Once connected, try a prompt like: + +``` +List users in my Appwrite project +``` + +# Self-hosting Appwrite? + +The remote server authenticates against Appwrite Cloud. If you run a [self-hosted Appwrite instance](/docs/advanced/self-hosting), the local MCP server is still available and works the way it always has: it runs on your machine over the stdio transport and connects to your instance with an API key. The [MCP server documentation](/docs/advanced/self-hosting/mcp) walks through the setup. + +# Resources + +- [MCP server documentation](/docs/tooling/ai/mcp-servers/api) +- [AI tooling docs](/docs/tooling/ai) +- [Announcing Appwrite MCP Server 2.0](/blog/post/announcing-appwrite-mcp-server-2) +- [Discord community](https://appwrite.io/discord) diff --git a/src/routes/changelog/(entries)/2026-07-31.markdoc b/src/routes/changelog/(entries)/2026-07-31.markdoc new file mode 100644 index 0000000000..222ea5be43 --- /dev/null +++ b/src/routes/changelog/(entries)/2026-07-31.markdoc @@ -0,0 +1,27 @@ +--- +layout: changelog +title: "The Appwrite MCP server is now remote" +date: 2026-07-31 +cover: /images/changelog/2026-07-31.avif +--- + +The [**Appwrite MCP server**](/docs/tooling/ai/mcp-servers/api) is now available as a **hosted remote server** over the HTTP transport at `https://mcp.appwrite.io/`. + +Previously, connecting an AI tool to your Appwrite project meant running the MCP server locally: installing **uv**, creating an **API key** with the right scopes, and adding your endpoint, project ID, and key to every tool's MCP configuration. + +The remote server removes all of that. You add **one URL** to your AI tool and sign in with **OAuth** in the browser. There is nothing to install, no keys to manage, and nothing to keep updated. + +The remote server keeps the **compact architecture** from [MCP Server 2.0](/blog/post/announcing-appwrite-mcp-server-2), exposing only a small set of MCP tools to the model: + +- `appwrite_get_context`: Returns a summary of your workspace, including your account, organization, and projects +- `appwrite_search_tools`: Searches the full Appwrite tool catalog at runtime +- `appwrite_call_tool`: Calls a specific Appwrite tool by name +- `appwrite_search_docs`: Semantically searches the Appwrite documentation + +All Appwrite services stay available without filling the model's context with unused tool definitions. Documentation search is built in, so the separate **Appwrite docs MCP server** is no longer needed: one connection covers both your project and the docs. + +If you run a [self-hosted Appwrite instance](/docs/advanced/self-hosting), the [local MCP server](/docs/advanced/self-hosting/mcp) is still available and connects to your instance with an API key. + +{% arrow_link href="/blog/post/announcing-remote-appwrite-mcp-server" %} +Read the blog announcement +{% /arrow_link %} diff --git a/src/routes/docs/advanced/self-hosting/+layout.svelte b/src/routes/docs/advanced/self-hosting/+layout.svelte index 5c2db920ca..e844ffa993 100644 --- a/src/routes/docs/advanced/self-hosting/+layout.svelte +++ b/src/routes/docs/advanced/self-hosting/+layout.svelte @@ -91,6 +91,15 @@ } ] }, + { + label: 'Tooling', + items: [ + { + label: 'MCP server', + href: '/docs/advanced/self-hosting/mcp' + } + ] + }, { label: 'Production', items: [ diff --git a/src/routes/docs/advanced/self-hosting/mcp/+page.markdoc b/src/routes/docs/advanced/self-hosting/mcp/+page.markdoc new file mode 100644 index 0000000000..d2833598f1 --- /dev/null +++ b/src/routes/docs/advanced/self-hosting/mcp/+page.markdoc @@ -0,0 +1,132 @@ +--- +layout: article +title: MCP server +description: Connect LLMs and code-generation tools to your self-hosted Appwrite instance with the local MCP server. +--- + +The [hosted Appwrite MCP server](/docs/tooling/ai/mcp-servers/api) authenticates against Appwrite Cloud. If you are running a self-hosted Appwrite instance, use the local MCP server instead. It runs on your machine over the stdio transport and connects to your instance with an API key, allowing LLMs and code-generation tools to perform various operations on your Appwrite resources, such as creating users, managing databases, and more, using natural language commands. + +Here are some of the key benefits of using the local MCP server: + +- **Direct API interaction**: Enables LLMs to perform actions directly on your Appwrite project +- **Real-time data access**: Allows LLMs to fetch and manipulate live data from your Appwrite instance +- **Simplified workflows**: Facilitates complex operations through simple natural language prompts +- **Customizable tools**: Offers a range of tools for different Appwrite services, which can be enabled as needed + +# Pre-requisites {% #pre-requisites %} + +## Appwrite API key + +Before launching the MCP server, create an **API key** with the necessary scopes enabled in your Appwrite project. + +{% only_light %} +![Appwrite API key](/images/docs/mcp/appwrite/appwrite-api-secret.avif) +{% /only_light %} +{% only_dark %} +![Appwrite API key](/images/docs/mcp/appwrite/dark/appwrite-api-secret.avif) +{% /only_dark %} + +Ensure you save the **API key** along with the **project ID** and **endpoint URL** from the Settings page of your project as you'll need them later. + +## Install uv + +Install [uv](https://docs.astral.sh/uv/getting-started/installation/) on your system with: + +{% tabs %} +{% tabsitem #uv-linux-macos title="Linux and MacOS" %} + +```bash +curl -LsSf https://astral.sh/uv/install.sh | sh +``` + +{% /tabsitem %} + +{% tabsitem #uv-windows title="Windows" %} + +```powershell +powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex" +``` + +{% /tabsitem %} +{% /tabs %} + +You can verify the installation by running the following command in your terminal: + +```bash +uv +``` + +# Installation {% #installation %} + +Add the local MCP server to your AI tool's MCP configuration: + +```json +{ + "mcpServers": { + "appwrite": { + "command": "uvx", + "args": [ + "mcp-server-appwrite" + ], + "env": { + "APPWRITE_PROJECT_ID": "your-project-id", + "APPWRITE_API_KEY": "your-api-key", + "APPWRITE_ENDPOINT": "https://your-appwrite-domain/v1" + } + } + } +} +``` + +Replace `your-project-id` and `your-api-key` with the values from your project, and point `APPWRITE_ENDPOINT` to your instance's API endpoint. + +## Command-line arguments + +Database tools are enabled by default. In addition you can pass arguments to `uvx mcp-server-appwrite [args]` to enable other MCP tools for various Appwrite APIs. + +| Argument | Description | +| --- | --- | +| `--tablesdb` | Enables the TablesDB API | +| `--users` | Enables the Users API | +| `--teams` | Enables the Teams API | +| `--storage` | Enables the Storage API | +| `--functions` | Enables the Functions API | +| `--messaging` | Enables the Messaging API | +| `--locale` | Enables the Locale API | +| `--avatars` | Enables the Avatars API | +| `--databases` | Enables the legacy Databases API | +| `--all` | Enables all Appwrite APIs | + +{% info title="Enable only necessary MCP tools" %} +When an MCP tool is enabled, the tool's definition is passed to the LLM, using up tokens from the model's available context window. As a result, the effective context window is reduced. Some IDEs may return errors if too many tools are enabled for the same reason. + +The default Appwrite MCP server ships with only the Databases tools (our most commonly used API) enabled to stay within these limits. Additional tools can be enabled using the flags above. +{% /info %} + +# Usage {% #usage %} + +Once configured, your AI assistant will have access to your Appwrite project. You can ask questions like: + +## Example 1: List users + +Run the following prompt in your preferred code editor/LLM after enabling the MCP server: + +``` +List users in my Appwrite project +``` + +## Example 2: Search a site + +Run the following prompt in your preferred code editor/LLM after enabling the MCP server: + +``` +Get the details of my portfolio site from Appwrite +``` + +## Example 3: Create a user + +Run the following prompt in your preferred code editor/LLM after enabling the MCP server: + +``` +Add a user john.doe@example.com to the Appwrite project +``` diff --git a/src/routes/docs/tooling/ai/+layout.svelte b/src/routes/docs/tooling/ai/+layout.svelte index 69f0b369f7..0ce74952a6 100644 --- a/src/routes/docs/tooling/ai/+layout.svelte +++ b/src/routes/docs/tooling/ai/+layout.svelte @@ -76,6 +76,10 @@ { label: 'Google Antigravity', href: '/docs/tooling/ai/agents/antigravity' + }, + { + label: 'Grok Build', + href: '/docs/tooling/ai/agents/grok-build' } ] }, diff --git a/src/routes/docs/tooling/ai/+page.markdoc b/src/routes/docs/tooling/ai/+page.markdoc index 97d9884c66..f3c8c8d78e 100644 --- a/src/routes/docs/tooling/ai/+page.markdoc +++ b/src/routes/docs/tooling/ai/+page.markdoc @@ -8,7 +8,7 @@ Appwrite provides a comprehensive set of tools and resources to help you build w # IDEs {% #ides %} -AI-powered IDEs and code editors provide intelligent code completion and context-aware assistance as you write code. These tools support our MCP servers, giving AI agents direct access to your Appwrite project. +AI-powered IDEs and code editors provide intelligent code completion and context-aware assistance as you write code. These tools support the Appwrite MCP server, giving AI agents direct access to your Appwrite project and documentation. {% only_light %} {% cards %} @@ -34,6 +34,9 @@ AI-powered IDEs and code editors provide intelligent code completion and context {% cards_item href="/docs/tooling/ai/agents/antigravity" title="Antigravity" image="/images/docs/mcp/logos/google-antigravity.svg" %} {% /cards_item %} +{% cards_item href="/docs/tooling/ai/agents/grok-build" title="Grok Build" image="/images/docs/mcp/logos/grok-build.svg" %} +{% /cards_item %} + {% /cards %} {% /only_light %} @@ -61,6 +64,9 @@ AI-powered IDEs and code editors provide intelligent code completion and context {% cards_item href="/docs/tooling/ai/agents/antigravity" title="Antigravity" image="/images/docs/mcp/logos/dark/google-antigravity.svg" %} {% /cards_item %} +{% cards_item href="/docs/tooling/ai/agents/grok-build" title="Grok Build" image="/images/docs/mcp/logos/dark/grok-build.svg" %} +{% /cards_item %} + {% /cards %} {% /only_dark %} @@ -118,7 +124,7 @@ These resources help AI tools understand and work with Appwrite. Use them alongs {% cards_item href="/docs/tooling/ai/quickstart-prompts" title="Quickstart prompts" %} Pre-built prompts to quickly generate your first Appwrite project with AI assistants. {% /cards_item %} -{% cards_item href="/docs/tooling/ai/mcp-servers/api" title="MCP servers" %} +{% cards_item href="/docs/tooling/ai/mcp-servers/api" title="MCP server" %} Give AI tools direct access to your Appwrite project and docs. {% /cards_item %} {% cards_item href="/docs/tooling/ai/agents-md" title="AGENTS.md" %} diff --git a/src/routes/docs/tooling/ai/agents/antigravity/+page.markdoc b/src/routes/docs/tooling/ai/agents/antigravity/+page.markdoc index a12dc4d0dd..976bdc3400 100644 --- a/src/routes/docs/tooling/ai/agents/antigravity/+page.markdoc +++ b/src/routes/docs/tooling/ai/agents/antigravity/+page.markdoc @@ -1,7 +1,7 @@ --- layout: article title: Google Antigravity -description: Learn how you can add the Appwrite MCP servers to Agent Manager in Google Antigravity to interact with both the Appwrite API and documentation. +description: Learn how you can add the Appwrite MCP server to Agent Manager in Google Antigravity to interact with both the Appwrite API and documentation. --- {% section #quick-start-prompts step=1 title="Quick start prompts" %} @@ -21,81 +21,32 @@ Browse all quick start prompts {% /section %} -{% section #step-2 step=2 title="Add MCP servers" %} +{% section #step-2 step=2 title="Add the MCP server" %} -Connect Appwrite MCP servers to Antigravity for deeper integration with the Appwrite API and documentation. - -Before you begin, ensure you have the following **pre-requisites** installed on your system: - -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} - -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. - -{% /tabsitem %} - -{% tabsitem #docs-server-prerequisites title="Docs server" %} - -[Node.js](https://nodejs.org/en/download) and npm must be installed on your system. - -{% /tabsitem %} -{% /tabs %} +Connect the Appwrite MCP server to Antigravity for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. To add the Appwrite MCP server, open Antigravity and go to the drop-down (...) menu in the Agent window . From there, navigate to Manage MCP Servers in the MCP Store, and then click View raw config in the main panel to add your custom MCP server. -{% tabs %} -{% tabsitem #api-only title="API server" %} - -Update the `mcp_config.json` file to include the API server: +Update the `mcp_config.json` file to include the Appwrite MCP server: ```json { "mcpServers": { - "appwrite-api": { - "command": "uvx", - "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_PROJECT_ID": "your-project-id", - "APPWRITE_API_KEY": "your-api-key", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } + "appwrite": { + "serverUrl": "https://mcp.appwrite.io/" } } } ``` -**Configuration:** - -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `nyc`, `fra`) +{% info title="Use the serverUrl key" %} -{% /tabsitem %} +Antigravity requires the `serverUrl` key for remote MCP servers. Using fields like `url` or `httpUrl` will cause tool registration to fail silently. -{% tabsitem #docs-only title="Docs server" %} +{% /info %} -Update the `mcp_config.json` file to include the docs server: - -```json -{ - "mcpServers": { - "appwrite-docs": { - "command": "npx", - "args": [ - "mcp-remote", - "" - ] - } - } -} - -``` - -{% /tabsitem %} -{% /tabs %} +The server uses OAuth for authentication. When Antigravity first connects to the server, your browser opens so you can sign in to your Appwrite account and authorize access. Head back to the Managed MCP Server page and click refresh. @@ -103,35 +54,15 @@ Head back to the Managed MCP Server page and click refresh. {% section #step-3 step=3 title="Test the integration" %} -Open **Agent Manager** in Antigravity to test your MCP integrations. You can try out the following example prompts based on the MCP server you have configured: - -{% tabs %} -{% tabsitem #test-api title="API server" %} +Open **Agent Manager** in Antigravity to test your MCP integration. You can try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} - -![Antigravity Agent chat](/images/docs/mcp/antigravity/agent-chat.avif) {% /section %} \ No newline at end of file diff --git a/src/routes/docs/tooling/ai/agents/claude-code/+page.markdoc b/src/routes/docs/tooling/ai/agents/claude-code/+page.markdoc index 06f747a41f..9a1ba54de6 100644 --- a/src/routes/docs/tooling/ai/agents/claude-code/+page.markdoc +++ b/src/routes/docs/tooling/ai/agents/claude-code/+page.markdoc @@ -1,40 +1,10 @@ --- layout: article title: Claude Code -description: Learn how to use Claude Code with Appwrite through the Appwrite plugin, quick start prompts, and MCP servers for AI-assisted development. +description: Learn how to use Claude Code with Appwrite through quick start prompts and the Appwrite MCP server for AI-assisted development. --- -{% section #install-plugin step=1 title="Install the Appwrite plugin" %} - -The fastest way to get started with Appwrite in Claude Code is to install the [**Appwrite plugin**](https://claude.com/plugins/appwrite) from the official marketplace. The plugin includes agent skills for the CLI and all major SDKs and sets up MCP servers for both the Appwrite API and documentation, giving Claude Code everything it needs to work with your Appwrite projects. - -To install the plugin, run the following command in your terminal: - -```bash -claude plugin install appwrite@claude-plugins-official -``` - -Once installed, run Claude Code and configure the plugin: - -- Run `/plugins` in Claude Code. -- Go to the **Installed** tab. -- Select the **Appwrite** plugin from the list. -- Choose **Configure options**. -- Enter your Appwrite endpoint, project ID, and API key when prompted. - -![Configure the Appwrite plugin in Claude Code](/images/docs/mcp/claude-code/configure-plugin.avif) - -After saving the configuration, run `/reload-plugins` to apply the changes to your current session. The `appwrite-api` MCP server will be ready alongside the agent skills, and Claude Code can now interact with your Appwrite project. - -{% info title="Prefer manual setup?" %} - -If you'd rather configure MCP servers individually, skip to [Step 3](#step-3). - -{% /info %} - -{% /section %} - -{% section #quick-start-prompts step=2 title="Quick start prompts" %} +{% section #quick-start-prompts step=1 title="Quick start prompts" %} Get started quickly with these pre-built prompts for common Appwrite integrations: @@ -51,98 +21,43 @@ Browse all quick start prompts {% /section %} -{% section #step-3 step=3 title="Add MCP servers manually" %} - -If you installed the Appwrite plugin in [Step 1](#install-plugin), MCP servers are already configured and you can skip to [Step 4](#step-4). - -Connect Appwrite MCP servers to Claude Code for deeper integration with the Appwrite API and documentation. - -Before you begin, ensure you have the following **pre-requisites** installed on your system: - -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} - -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. - -{% /tabsitem %} +{% section #step-2 step=2 title="Add the MCP server" %} -{% tabsitem #docs-server-prerequisites title="Docs server" %} +Connect the Appwrite MCP server to Claude Code for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. -[Node.js](https://nodejs.org/en/download) and npm must be installed on your system. - -{% /tabsitem %} -{% /tabs %} - -Run the following commands in your terminal to add the MCP servers: - -{% tabs %} -{% tabsitem #api-only title="API server" %} +Run the following command in your terminal to add the MCP server: ```bash -claude mcp add-json appwrite-api '{"command":"uvx","args":["mcp-server-appwrite"],"env":{"APPWRITE_PROJECT_ID": "your-project-id", "APPWRITE_API_KEY": "your-api-key", "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1"}}' - +claude mcp add --transport http appwrite https://mcp.appwrite.io/ ``` -{% /tabsitem %} - -{% tabsitem #docs-only title="Docs server" %} - -```bash -claude mcp add appwrite-docs -t http - -``` - -{% /tabsitem %} -{% /tabs %} +The server uses OAuth for authentication. Run `/mcp` in Claude Code, select **appwrite**, and choose **Authenticate**. Your browser opens so you can sign in to your Appwrite account and authorize access. {% /section %} -{% section #step-4 step=4 title="Verify MCP tools" %} +{% section #step-3 step=3 title="Verify MCP tools" %} Run the following command in your terminal (where Claude Code is running). ```bash /mcp - ``` -You should see the added MCP servers listed there. - -![Verify MCP tools](/images/docs/mcp/claude-code/verify-mcp-tools.avif) +You should see the added MCP server listed there. {% /section %} -{% section #step-5 step=5 title="Test the integration" %} - -Try out the following example prompts based on the MCP server you have configured: +{% section #step-4 step=4 title="Test the integration" %} -{% tabs %} -{% tabsitem #test-api title="API server" %} +Try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} - -![Implement file uploads](/images/docs/mcp/claude-code/implement-file-uploads.avif) {% /section %} diff --git a/src/routes/docs/tooling/ai/agents/codex/+page.markdoc b/src/routes/docs/tooling/ai/agents/codex/+page.markdoc index 5545d67a58..be26ad2529 100644 --- a/src/routes/docs/tooling/ai/agents/codex/+page.markdoc +++ b/src/routes/docs/tooling/ai/agents/codex/+page.markdoc @@ -1,38 +1,10 @@ --- layout: article title: Codex -description: Learn how to use Codex with Appwrite through the Appwrite plugin, quick start prompts, and MCP servers for AI-assisted development. +description: Learn how to use Codex with Appwrite through quick start prompts and the Appwrite MCP server for AI-assisted development. --- -{% section #install-plugin step=1 title="Install the Appwrite plugin" %} - -The fastest way to get started with Appwrite in Codex is to install the **Appwrite plugin** from the Appwrite marketplace. The plugin includes agent skills for the Appwrite CLI and all major SDKs and registers the Appwrite Docs MCP server, giving Codex access to the Appwrite documentation so that it follows the latest and suggested code patterns. - -Add the Appwrite marketplace to Codex by running the following command in your terminal: - -```bash -codex plugin marketplace add appwrite/codex-plugin -``` - -Then run `codex` and open the plugins menu to install the Appwrite plugin: - -- Run `/plugins` in Codex. -- Select the **Appwrite** plugin from the marketplace listing. -- Confirm the install. - -Once installed, the language and deployment skills load automatically based on your task, and the `appwrite-docs` MCP server is registered for documentation lookups. - -The Appwrite API MCP server isn't bundled in the plugin: it needs your endpoint, project ID, and API key, and Codex plugins don't currently expose a way to prompt for per-install configuration in the CLI. Add it manually in [Step 3](#step-3). - -{% info title="Prefer manual setup?" %} - -If you'd rather configure MCP servers individually, skip to [Step 3](#step-3). - -{% /info %} - -{% /section %} - -{% section #quick-start-prompts step=2 title="Quick start prompts" %} +{% section #quick-start-prompts step=1 title="Quick start prompts" %} Get started quickly with these pre-built prompts for common Appwrite integrations: @@ -49,91 +21,35 @@ Browse all quick start prompts {% /section %} -{% section #step-3 step=3 title="Add MCP servers manually" %} - -If you installed the Appwrite plugin in [Step 1](#install-plugin), the docs MCP server is already configured and you can skip to [Step 4](#step-4). - -Connect Appwrite MCP servers to Codex for deeper integration with the Appwrite API and documentation. - -Before you begin, ensure you have the following **pre-requisites** installed on your system: - -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} +{% section #step-2 step=2 title="Add the MCP server" %} -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. +Connect the Appwrite MCP server to Codex for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. -{% /tabsitem %} - -{% tabsitem #docs-server-prerequisites title="Docs server" %} - -No additional prerequisites. The docs server runs as a remote HTTP endpoint. - -{% /tabsitem %} -{% /tabs %} - -Run the following commands in your terminal to add the MCP servers: - -{% tabs %} -{% tabsitem #api-only title="API server" %} +Run the following command in your terminal to add the MCP server: ```bash -codex mcp add appwrite-api \ - --env APPWRITE_PROJECT_ID=your-project-id \ - --env APPWRITE_API_KEY=your-api-key \ - --env APPWRITE_ENDPOINT=https://.cloud.appwrite.io/v1 \ - -- uvx mcp-server-appwrite +codex mcp add appwrite --url https://mcp.appwrite.io/ ``` -**Configuration:** - -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `nyc`, `fra`) - -{% /tabsitem %} - -{% tabsitem #docs-only title="Docs server" %} +The server uses OAuth for authentication. In case Codex does not automatically prompt you to login, run the following command to sign in to your Appwrite account and authorize access: ```bash -codex mcp add appwrite-docs --url https://mcp-for-docs.appwrite.io +codex mcp login appwrite ``` -{% /tabsitem %} -{% /tabs %} - {% /section %} -{% section #step-4 step=4 title="Test the integration" %} +{% section #step-3 step=3 title="Test the integration" %} -Try out the following example prompts based on the MCP server you have configured: - -{% tabs %} -{% tabsitem #test-api title="API server" %} +Try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} - -![Codex listing users via the Appwrite API MCP](/images/docs/mcp/codex/test-integration.avif) {% /section %} diff --git a/src/routes/docs/tooling/ai/agents/cursor/+page.markdoc b/src/routes/docs/tooling/ai/agents/cursor/+page.markdoc index 158212065c..e5d971d4dd 100644 --- a/src/routes/docs/tooling/ai/agents/cursor/+page.markdoc +++ b/src/routes/docs/tooling/ai/agents/cursor/+page.markdoc @@ -1,31 +1,10 @@ --- layout: article title: Cursor -description: Learn how to use Cursor with Appwrite through the Appwrite plugin, quick start prompts, and MCP servers for AI-assisted development. +description: Learn how to use Cursor with Appwrite through quick start prompts and the Appwrite MCP server for AI-assisted development. --- -{% section #install-plugin step=1 title="Install the Appwrite plugin" %} - -The fastest way to get started with Appwrite in Cursor is to install the **Appwrite plugin** from the Cursor Marketplace. The plugin includes agent skills, MCP servers, and commands, giving Cursor's AI agents everything they need to work with your Appwrite projects. - -To install the plugin: - -1. Visit the [Appwrite plugin](https://cursor.com/marketplace/appwrite) page on the Cursor Marketplace. -2. Sign in with your Cursor account. -3. Click **Add to Cursor**. -4. The plugin will be added to your editor automatically. - -Once installed, the plugin gives your AI agents access to Appwrite skills for all major SDKs, MCP servers for the Appwrite API and documentation, and commands for deploying functions and sites. - -{% info title="Prefer manual setup?" %} - -If you'd rather configure MCP servers individually, skip to [Step 3](#step-3). - -{% /info %} - -{% /section %} - -{% section #quick-start-prompts step=2 title="Quick start prompts" %} +{% section #quick-start-prompts step=1 title="Quick start prompts" %} Get started quickly with these pre-built prompts for common Appwrite integrations: @@ -42,95 +21,33 @@ Browse all quick start prompts {% /section %} -{% section #step-3 step=3 title="Add MCP servers manually" %} - -If you installed the Appwrite plugin in [Step 1](#install-plugin), MCP servers are already configured and you can skip to [Step 4](#step-4). - -Connect Appwrite MCP servers to Cursor for deeper integration with the Appwrite API and documentation. +{% section #step-2 step=2 title="Add the MCP server" %} -Before you begin, ensure you have the following **pre-requisites** installed on your system: - -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} - -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. - -{% /tabsitem %} - -{% tabsitem #docs-server-prerequisites title="Docs server" %} - -[Node.js](https://nodejs.org/en/download) and npm must be installed on your system. - -{% /tabsitem %} -{% /tabs %} +Connect the Appwrite MCP server to Cursor for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. Open the **Cursor Settings** page, head to the **MCP** tab, and click on the **Add new global MCP server** button. This will open an `mcp.json` file in your editor. -Choose which MCP server you want to configure: - -{% tabs %} -{% tabsitem #api-only title="API server" %} - -Update the `mcp.json` file to include the API server: +Update the `mcp.json` file to include the Appwrite MCP server: ```json { "mcpServers": { - "appwrite-api": { - "command": "uvx", - "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_API_KEY": "your-api-key", - "APPWRITE_PROJECT_ID": "your-project-id", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } + "appwrite": { + "url": "https://mcp.appwrite.io/" } } } ``` -**Configuration:** - -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `nyc`, `fra`) - -{% /tabsitem %} - -{% tabsitem #docs-only title="Docs server" %} +The server uses OAuth for authentication. After you save the file, click **Needs login** next to the server in the MCP settings. Your browser opens so you can sign in to your Appwrite account and authorize access. -Update the `mcp.json` file to include the docs server: - -```json -{ - "mcpServers": { - "appwrite-docs": { - "command": "npx", - "args": [ - "mcp-remote", - "" - ] - } - } -} - -``` - -{% /tabsitem %} -{% /tabs %} - -You can also **directly add the MCP servers to Cursor** using the following links: +You can also **directly add the MCP server to Cursor** using the following link: {% only_light %} {% cards %} -{% cards_item href="https://apwr.dev/api-mcp-cursor?ref=docs" title="API server" image="/images/docs/mcp/logos/cursor-ai.svg" %} -{% /cards_item %} - -{% cards_item href="https://apwr.dev/docs-mcp-cursor?ref=docs" title="Docs server" image="/images/docs/mcp/logos/cursor-ai.svg" %} +{% cards_item href="https://cursor.com/install-mcp?name=appwrite&config=eyJ1cmwiOiJodHRwczovL21jcC5hcHB3cml0ZS5pby8ifQ==" title="Add to Cursor" image="/images/docs/mcp/logos/cursor-ai.svg" %} {% /cards_item %} {% /cards %} @@ -139,50 +56,27 @@ You can also **directly add the MCP servers to Cursor** using the following link {% only_dark %} {% cards %} -{% cards_item href="https://apwr.dev/api-mcp-cursor?ref=docs" title="API server" image="/images/docs/mcp/logos/dark/cursor-ai.svg" %} -{% /cards_item %} - -{% cards_item href="https://apwr.dev/docs-mcp-cursor?ref=docs" title="Docs server" image="/images/docs/mcp/logos/dark/cursor-ai.svg" %} +{% cards_item href="https://cursor.com/install-mcp?name=appwrite&config=eyJ1cmwiOiJodHRwczovL21jcC5hcHB3cml0ZS5pby8ifQ==" title="Add to Cursor" image="/images/docs/mcp/logos/dark/cursor-ai.svg" %} {% /cards_item %} {% /cards %} {% /only_dark %} -Once you save the details, Cursor will connect with the MCP server(s) and load all available tools. You may need to restart Cursor if it is unable to start the MCP server. +Once you save the details, Cursor will connect with the MCP server and load all available tools. You may need to restart Cursor if it is unable to start the MCP server. {% /section %} -{% section #step-4 step=4 title="Test the integration" %} - -Open Cursor Agent and test your MCP integrations. You can try out the following example prompts based on the MCP server you have configured: +{% section #step-3 step=3 title="Test the integration" %} -{% tabs %} -{% tabsitem #test-api title="API server" %} +Open Cursor Agent and test your MCP integration. You can try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} - -![Create a new user in Appwrite project](/images/docs/mcp/cursor/cursor-create-user.avif) {% /section %} \ No newline at end of file diff --git a/src/routes/docs/tooling/ai/agents/grok-build/+page.markdoc b/src/routes/docs/tooling/ai/agents/grok-build/+page.markdoc new file mode 100644 index 0000000000..2bb44247e5 --- /dev/null +++ b/src/routes/docs/tooling/ai/agents/grok-build/+page.markdoc @@ -0,0 +1,54 @@ +--- +layout: article +title: Grok Build +description: Learn how you can add the Appwrite MCP server to Grok Build to interact with both the Appwrite API and documentation. +--- + +{% section #quick-start-prompts step=1 title="Quick start prompts" %} + +Get started quickly with these pre-built prompts for common Appwrite integrations: + +{% cards %} +{% cards_item href="/docs/tooling/ai/quickstart-prompts/nextjs" title="Next.js" icon="icon-nextjs" %} +{% /cards_item %} +{% cards_item href="/docs/tooling/ai/quickstart-prompts/tanstack-start" title="TanStack Start" icon="web-icon-tanstack" %} +{% /cards_item %} +{% /cards %} + +{% arrow_link href="/docs/tooling/ai/quickstart-prompts" %} +Browse all quick start prompts +{% /arrow_link %} + +{% /section %} + +{% section #step-2 step=2 title="Add the MCP server" %} + +Connect the Appwrite MCP server to Grok Build for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. + +Run the following command in your terminal to add the MCP server: + +```bash +grok mcp add --transport http appwrite https://mcp.appwrite.io/ + +``` + +The server uses OAuth for authentication. When Grok Build first connects to the server, your browser opens so you can sign in to your Appwrite account and authorize access. In case you are not prompted automatically, run `/mcps` in Grok Build, select **appwrite**, and press `i` to authenticate. + +You can verify the server is configured by running `grok mcp list` in your terminal or `/mcps` in a Grok Build session. + +{% /section %} + +{% section #step-3 step=3 title="Test the integration" %} + +Open a Grok Build session by running `grok` in your terminal and test your MCP integration. You can try out the following example prompts: + +**Example prompts:** + +- `Create a new user in my Appwrite project` +- `List all databases in my project` +- `Show me the tables in my database` +- `How do I set up real-time subscriptions in Appwrite?` +- `Show me how to authenticate users with OAuth` +- `How do I implement file uploads with Appwrite Storage?` + +{% /section %} diff --git a/src/routes/docs/tooling/ai/agents/opencode/+page.markdoc b/src/routes/docs/tooling/ai/agents/opencode/+page.markdoc index 2b77c4e64d..7c6cf6c202 100644 --- a/src/routes/docs/tooling/ai/agents/opencode/+page.markdoc +++ b/src/routes/docs/tooling/ai/agents/opencode/+page.markdoc @@ -21,112 +21,42 @@ Browse all quick start prompts {% /section %} -{% section #step-2 step=2 title="Add MCP servers" %} +{% section #step-2 step=2 title="Add the MCP server" %} -Connect Appwrite MCP servers to OpenCode for deeper integration with the Appwrite API and documentation. +Connect the Appwrite MCP server to OpenCode for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. -Before you begin, ensure you have the following **pre-requisites** installed on your system: - -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} - -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. - -{% /tabsitem %} - -{% tabsitem #docs-server-prerequisites title="Docs server" %} - -[Node.js](https://nodejs.org/en/download) and npm must be installed on your system. - -{% /tabsitem %} -{% /tabs %} - -Use the following configuration in your `opencode.json` file to use the Appwrite MCP servers. - -{% tabs %} -{% tabsitem #api-only title="API server" %} +Use the following configuration in your `opencode.json` file to use the Appwrite MCP server. ```json { - "$schema": "", + "$schema": "https://opencode.ai/config.json", "mcp": { "appwrite": { - "type": "local", - "command": [ - "uvx", - "mcp-server-appwrite" - ], - "enabled": true, - "environment": { - "APPWRITE_PROJECT_ID": "your-project-id", - "APPWRITE_API_KEY": "your-api-key", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } - } - } -} - -``` - -**Configuration:** - -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `nyc`, `fra`) - -{% /tabsitem %} - -{% tabsitem #docs-only title="Docs server" %} - -```json -{ - "$schema": "", - "mcp": { - "appwrite-docs": { "type": "remote", "enabled": true, - "url": "" + "url": "https://mcp.appwrite.io/" } } } ``` -{% /tabsitem %} -{% /tabs %} +The server uses OAuth for authentication. When OpenCode first connects to the server, complete the sign-in flow in your browser to sign in to your Appwrite account and authorize access. {% /section %} {% section #step-3 step=3 title="Test the integration" %} -Try out the following example prompts based on the MCP server you have configured: - -{% tabs %} -{% tabsitem #test-api title="API server" %} +Try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} ![OAuth question in OpenCode](/images/docs/mcp/opencode/oauth-question.avif) diff --git a/src/routes/docs/tooling/ai/agents/vscode/+page.markdoc b/src/routes/docs/tooling/ai/agents/vscode/+page.markdoc index 8d36c435d7..4e18e05620 100644 --- a/src/routes/docs/tooling/ai/agents/vscode/+page.markdoc +++ b/src/routes/docs/tooling/ai/agents/vscode/+page.markdoc @@ -21,71 +21,19 @@ Browse all quick start prompts {% /section %} -{% section #add-mcp-servers step=2 title="Add MCP servers" %} +{% section #add-mcp-servers step=2 title="Add the MCP server" %} -Connect Appwrite MCP servers to VS Code for deeper integration with the Appwrite API and documentation. - -Before you begin, ensure you have the following **pre-requisites** installed on your system: - -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} - -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. - -{% /tabsitem %} - -{% tabsitem #docs-server-prerequisites title="Docs server" %} - -[Node.js](https://nodejs.org/en/download) and npm must be installed on your system. - -{% /tabsitem %} -{% /tabs %} +Connect the Appwrite MCP server to VS Code for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. In VS Code, open the **Command Palette** (press `CTRL + Shift + P` on Windows or `CMD + Shift + P` on MacOS) and run the `MCP: Open User Configuration` command. -Choose which MCP servers you want to configure: - -{% tabs %} -{% tabsitem #api-only title="API server" %} - -Update the `mcp.json` file to include the API server: - -```json -{ - "servers": { - "appwrite-api": { - "command": "uvx", - "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_PROJECT_ID": "your-project-id", - "APPWRITE_API_KEY": "your-api-key", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } - } - } -} - -``` - -**Configuration:** - -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `nyc`, `fra`) - -{% /tabsitem %} - -{% tabsitem #docs-only title="Docs server" %} - -Update the `mcp.json` file to include the docs server: +Update the `mcp.json` file to include the Appwrite MCP server: ```json { "servers": { - "appwrite-docs": { - "url": "", + "appwrite": { + "url": "https://mcp.appwrite.io/", "type": "http" } } @@ -93,44 +41,23 @@ Update the `mcp.json` file to include the docs server: ``` -{% /tabsitem %} -{% /tabs %} +The server uses OAuth for authentication. When the server starts, VS Code prompts you to authenticate, and your browser opens so you can sign in to your Appwrite account and authorize access. -Once you save the configuration, Copilot Chat will connect with the MCP server(s) and load all available tools. +Once you save the configuration, Copilot Chat will connect with the MCP server and load all available tools. {% /section %} {% section #test-the-integration step=3 title="Test the integration" %} -Open **Copilot Chat** in VS Code and switch to **Agent Mode** to test your MCP integrations. You can try out the following example prompts based on the MCP server you have configured: - -{% tabs %} -{% tabsitem #test-api title="API server" %} +Open **Copilot Chat** in VS Code and switch to **Agent Mode** to test your MCP integration. You can try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} - -![Search for portfolio site in Appwrite project](/images/docs/mcp/vscode/copilot-chat.avif) {% /section %} \ No newline at end of file diff --git a/src/routes/docs/tooling/ai/agents/windsurf/+page.markdoc b/src/routes/docs/tooling/ai/agents/windsurf/+page.markdoc index 1779be52ca..9c164225c9 100644 --- a/src/routes/docs/tooling/ai/agents/windsurf/+page.markdoc +++ b/src/routes/docs/tooling/ai/agents/windsurf/+page.markdoc @@ -21,81 +21,28 @@ Browse all quick start prompts {% /section %} -{% section #add-mcp-servers step=2 title="Add MCP servers" %} +{% section #add-mcp-servers step=2 title="Add the MCP server" %} -Connect Appwrite MCP servers to Windsurf for deeper integration with the Appwrite API and documentation. - -Before you begin, ensure you have the following **pre-requisites** installed on your system: - -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} - -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. - -{% /tabsitem %} - -{% tabsitem #docs-server-prerequisites title="Docs server" %} - -[Node.js](https://nodejs.org/en/download) and npm must be installed on your system. - -{% /tabsitem %} -{% /tabs %} +Connect the Appwrite MCP server to Windsurf for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. Open the **Windsurf Settings** page, head to the **Cascade** tab, find the **Model Context Protocol (MCP) Servers** section, and click on the **View raw config** button. ![Windsurf add MCP server](/images/docs/mcp/windsurf/windsurf-add-mcp-server.avif) -Choose which MCP server you want to configure: - -{% tabs %} -{% tabsitem #api-only title="API server" %} - -Update the `mcp_config.json` file to include the API server: - -```json -{ - "mcpServers": { - "appwrite-api": { - "command": "uvx", - "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_PROJECT_ID": "your-project-id", - "APPWRITE_API_KEY": "your-api-key", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } - } - } -} - -``` - -**Configuration:** - -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `nyc`, `fra`) - -{% /tabsitem %} - -{% tabsitem #docs-only title="Docs server" %} - -Update the `mcp_config.json` file to include the docs server: +Update the `mcp_config.json` file to include the Appwrite MCP server: ```json { "mcpServers": { - "appwrite-docs": { - "serverUrl": "" + "appwrite": { + "serverUrl": "https://mcp.appwrite.io/" } } } ``` -{% /tabsitem %} -{% /tabs %} +The server uses OAuth for authentication. When Windsurf first connects to the server, you are prompted to log in, and your browser opens so you can sign in to your Appwrite account and authorize access. Once you save the details, head back to the MCP Servers section in the Windsurf Settings and click on the **Refresh** button. @@ -103,35 +50,15 @@ Once you save the details, head back to the MCP Servers section in the Windsurf {% section #test-the-integration step=3 title="Test the integration" %} -Open Cascade chat in the Windsurf Editor and test your MCP integrations. You can try out the following example prompts based on the MCP server you have configured: - -{% tabs %} -{% tabsitem #test-api title="API server" %} +Open Cascade chat in the Windsurf Editor and test your MCP integration. You can try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} - -![Windsurf Cascade chat](/images/docs/mcp/windsurf/windsurf-cascade-chat.avif) {% /section %} \ No newline at end of file diff --git a/src/routes/docs/tooling/ai/agents/zed/+page.markdoc b/src/routes/docs/tooling/ai/agents/zed/+page.markdoc index d5a50cd532..73fc3eaff7 100644 --- a/src/routes/docs/tooling/ai/agents/zed/+page.markdoc +++ b/src/routes/docs/tooling/ai/agents/zed/+page.markdoc @@ -21,75 +21,26 @@ Browse all quick start prompts {% /section %} -{% section #step-2 step=2 title="Add MCP servers" %} +{% section #step-2 step=2 title="Add the MCP server" %} -Connect Appwrite MCP servers to Zed for deeper integration with the Appwrite API and documentation. +Connect the Appwrite MCP server to Zed for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. -Before you begin, ensure you have the following **pre-requisites** installed on your system: +In Zed, open the **Command Palette** (press `CMD + Shift + P` on MacOS or `CTRL + Shift + P` on Linux) and run the `agent: add context server` action. -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} - -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. - -{% /tabsitem %} - -{% tabsitem #docs-server-prerequisites title="Docs server" %} - -No additional prerequisites. The docs server runs as a remote HTTP endpoint. - -{% /tabsitem %} -{% /tabs %} - -In Zed, open the **Command Palette** (press `CMD + Shift + P` on MacOS or `CTRL + Shift + P` on Linux), run the `agent: add context server` action, and choose which MCP server you want to configure: - -{% tabs %} -{% tabsitem #api-only title="API server" %} - -In the **Local** tab, update the JSON configuration to include the API server: +In the **Remote** tab, update the JSON configuration to include the Appwrite MCP server: ```json { - "appwrite-api": { - "command": "uvx", - "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_PROJECT_ID": "your-project-id", - "APPWRITE_API_KEY": "your-api-key", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } + "appwrite": { + "url": "https://mcp.appwrite.io/" } } ``` -**Configuration:** +The server uses OAuth for authentication. When Zed first connects to the server, your browser opens so you can sign in to your Appwrite account and authorize access. -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `nyc`, `fra`) - -{% /tabsitem %} - -{% tabsitem #docs-only title="Docs server" %} - -In the **Remote** tab, update the JSON configuration to include the docs server: - -```json -{ - "appwrite-docs": { - "url": "https://mcp-for-docs.appwrite.io" - } -} - -``` - -{% /tabsitem %} -{% /tabs %} - -Click **Add Server** after adding each configuration. You can also review the configured servers in the **Model Context Protocol (MCP) Servers** section of Zed's Agent settings. +Click **Add Server** after adding the configuration. You can also review the configured server in the **Model Context Protocol (MCP) Servers** section of Zed's Agent settings. {% /section %} @@ -116,35 +67,15 @@ Zed loads skills from `~/.agents/skills/` for global installs and `/.a {% section #step-4 step=4 title="Test the integration" %} -Open the Agent panel in Zed and test your MCP integrations. You can try out the following example prompts based on the MCP server you have configured: - -{% tabs %} -{% tabsitem #test-api title="API server" %} +Open the Agent panel in Zed and test your MCP integration. You can try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} - -![Zed Agent using the Appwrite docs MCP](/images/docs/mcp/zed/zed-agent-chat.avif) {% /section %} diff --git a/src/routes/docs/tooling/ai/mcp-servers/+page.markdoc b/src/routes/docs/tooling/ai/mcp-servers/+page.markdoc index 36ba8c619b..c45b72e6e5 100644 --- a/src/routes/docs/tooling/ai/mcp-servers/+page.markdoc +++ b/src/routes/docs/tooling/ai/mcp-servers/+page.markdoc @@ -4,7 +4,7 @@ title: Model Context Protocol description: Enable LLMs and code-generation tools to interact with your Appwrite project --- -Appwrite offers [Model Context Protocol](https://modelcontextprotocol.io) (MCP) servers that allow LLMs to directly interact with Appwrite's API and docs. Using MCP servers, you can use applications such as Claude Code, Codex, Cursor, Claude Desktop, and others to operate on your Appwrite project as well as gain context about the latest updates to Appwrite's SDKs, APIs, and CLI. +Appwrite offers a [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server that allows LLMs to directly interact with Appwrite's API and docs. Using the MCP server, you can use applications such as Claude Code, Codex, Cursor, Claude Desktop, and others to operate on your Appwrite project as well as gain context about the latest updates to Appwrite's SDKs, APIs, and CLI. # What is MCP? @@ -16,23 +16,20 @@ The key benefits of using MCP servers include: - **Improved context**: By accessing up-to-date documentation and API definitions, LLMs can provide more accurate and relevant responses. - **Seamless integration**: MCP servers can be easily integrated with popular AI tools and code editors, enhancing their functionality. -# Available MCP servers +# The Appwrite MCP server -Appwrite currently offers the following MCP servers: +Appwrite offers a single MCP server that covers both the Appwrite API and documentation: {% cards %} -{% cards_item href="/docs/tooling/ai/mcp-servers/api" title="MCP server for Appwrite API" icon="icon-globe-alt"%} -{% /cards_item %} - -{% cards_item href="/docs/tooling/ai/mcp-servers/docs" title="MCP server for Appwrite docs" icon="icon-document-text" %} +{% cards_item href="/docs/tooling/ai/mcp-servers/api" title="Appwrite MCP server" icon="icon-globe-alt"%} {% /cards_item %} {% /cards %} -## Why use Appwrite's MCP servers? +## Why use the Appwrite MCP server? -Some **popular use cases** for Appwrite's MCP servers include: +Some **popular use cases** for the Appwrite MCP server include: - **Code generation**: Automatically generate code snippets or entire files based on user input and context. - **Documentation lookup**: Quickly find relevant documentation for specific API endpoints or SDK features. diff --git a/src/routes/docs/tooling/ai/mcp-servers/api/+page.markdoc b/src/routes/docs/tooling/ai/mcp-servers/api/+page.markdoc index 15382a615f..ab1402e927 100644 --- a/src/routes/docs/tooling/ai/mcp-servers/api/+page.markdoc +++ b/src/routes/docs/tooling/ai/mcp-servers/api/+page.markdoc @@ -1,60 +1,33 @@ --- layout: article -title: MCP server for Appwrite API -description: Enable LLMs and code-generation tools to interact with the Appwrite API +title: Appwrite MCP server +description: Enable LLMs and code-generation tools to interact with the Appwrite API and documentation --- -The MCP server for Appwrite API allows LLMs and code-generation tools to interact with the Appwrite platform and perform various operations on your Appwrite resources, such as creating users, managing databases, and more, using natural language commands. +The Appwrite MCP server allows LLMs and code-generation tools to interact with the Appwrite platform and perform various operations on your Appwrite resources, such as creating users, managing databases, and more, using natural language commands. It also gives them access to the Appwrite documentation, so they can look up the latest guidance for Appwrite's APIs and SDKs while they work. Here are some of the key benefits of using the MCP server: - **Direct API interaction**: Enables LLMs to perform actions directly on your Appwrite project - **Real-time data access**: Allows LLMs to fetch and manipulate live data from your Appwrite instance +- **Documentation search**: Lets LLMs semantically search the Appwrite documentation for accurate, up-to-date context - **Simplified workflows**: Facilitates complex operations through simple natural language prompts - **Automatic service discovery**: All supported Appwrite services are automatically registered, no configuration needed +- **No local setup**: Runs as a hosted HTTP service, so there is nothing to install or keep updated -# Pre-requisites {% #pre-requisites %} - -## Appwrite API key - -Before launching the MCP server, you must [set up an Appwrite project](https://cloud.appwrite.io) and create an **API key** with the necessary scopes enabled. - -{% only_light %} -![Appwrite API key](/images/docs/mcp/appwrite/appwrite-api-secret.avif) -{% /only_light %} -{% only_dark %} -![Appwrite API key](/images/docs/mcp/appwrite/dark/appwrite-api-secret.avif) -{% /only_dark %} - -Ensure you save the **API key** along with the **project ID**, **region** and **endpoint URL** from the Settings page of your project as you'll need them later. - -## Install uv +# Connection details {% #connection-details %} -Install [uv](https://docs.astral.sh/uv/getting-started/installation/) on your system with: +The Appwrite MCP server is a remote server that uses the HTTP transport. It is available at the following URL: -{% tabs %} -{% tabsitem #uv-linux-macos title="Linux and MacOS" %} - -```bash -curl -LsSf https://astral.sh/uv/install.sh | sh +``` +https://mcp.appwrite.io/ ``` -{% /tabsitem %} - -{% tabsitem #uv-windows title="Windows" %} - -```powershell -powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex" -``` - -{% /tabsitem %} -{% /tabs %} +The server uses OAuth for authentication. When you add the server to an AI tool and connect for the first time, your browser opens so you can sign in to your Appwrite account and authorize access. You don't need to create or manage API keys. -You can verify the installation by running the following command in your terminal: +# Pre-requisites {% #pre-requisites %} -```bash -uv -``` +Before connecting to the MCP server, you must [set up an Appwrite project](https://cloud.appwrite.io) on Appwrite Cloud. No additional software needs to be installed on your system. # Installation {% #installation %} @@ -62,13 +35,19 @@ uv ## How it works -The MCP server starts in a compact workflow where only two MCP tools are exposed to the model: +The MCP server starts in a compact workflow where only a small set of MCP tools is exposed to the model: +- `appwrite_get_context` - Returns a summary of your workspace, including your account, organization, and projects - `appwrite_search_tools` - Searches the full Appwrite tool catalog at runtime - `appwrite_call_tool` - Calls a specific Appwrite tool by name +- `appwrite_search_docs` - Semantically searches the Appwrite documentation The full Appwrite tool catalog stays internal and is searched at runtime, using less of the model's context. +# Self-hosted Appwrite {% #self-hosted %} + +The hosted MCP server authenticates against Appwrite Cloud. If you are running a [self-hosted Appwrite instance](/docs/advanced/self-hosting), use the local MCP server instead. It runs on your machine over the stdio transport and connects to your instance with an API key. Follow the [self-hosted MCP server documentation](/docs/advanced/self-hosting/mcp) to set it up. + # Usage {% #usage %} Once configured, your AI assistant will have access to your Appwrite project. You can ask questions like: @@ -81,8 +60,6 @@ Run the following prompt in your preferred code editor/LLM after enabling the MC List users in my Appwrite project ``` -![List users in Appwrite project](/images/docs/mcp/claude-desktop/claude-list-users.avif) - ## Example 2: Search a site Run the following prompt in your preferred code editor/LLM after enabling the MCP server: @@ -91,14 +68,18 @@ Run the following prompt in your preferred code editor/LLM after enabling the MC Get the details of my portfolio site from Appwrite ``` -![Search for portfolio site in Appwrite project](/images/docs/mcp/vscode/copilot-chat.avif) - ## Example 3: Create a user -Run the following prompt in your preferred code editor/LLM after enabling the MCP server: +Run the following prompt in your preferred code editor/LLM after enabling the MCP server: ``` Add a user john.doe@example.com to the Appwrite project ``` -![Create user in Appwrite project](/images/docs/mcp/cursor/cursor-create-user.avif) +## Example 4: Search the documentation + +Run the following prompt in your preferred code editor/LLM after enabling the MCP server: + +``` +Show me how to set up real-time subscriptions that trigger on creation of a user +``` diff --git a/src/routes/docs/tooling/ai/mcp-servers/docs/+page.markdoc b/src/routes/docs/tooling/ai/mcp-servers/docs/+page.markdoc index 3f8bf006fb..9652b325de 100644 --- a/src/routes/docs/tooling/ai/mcp-servers/docs/+page.markdoc +++ b/src/routes/docs/tooling/ai/mcp-servers/docs/+page.markdoc @@ -1,72 +1,21 @@ --- layout: article title: MCP server for Appwrite docs -description: Enable LLMs and code-generation tools to interact with the Appwrite docs +description: Appwrite documentation access is now part of the Appwrite MCP server --- -The MCP server for Appwrite documentation allows LLMs and code-generation tools to interact with comprehensive Appwrite documentation, enabling intelligent code generation for Appwrite's APIs and SDKs, troubleshooting assistance, and implementation guidance using natural language commands. - -Here are some of the key benefits of using the MCP server: - -- **Complete documentation access**: Provides AI assistants with access to all Appwrite documentation -- **Real-time context**: Ensures AI responses are based on the latest documentation -- **Intelligent search**: Enables semantic search across documentation content -- **Code examples**: Includes access to code samples and implementation guides -- **Best practices**: Shares recommended patterns and practices from official documentation - -# Pre-requisites {% #pre-requisites %} - -Install [Node.js](https://nodejs.org/en/download) and npm on your system. You can verify the installation by running the following commands in your terminal: - -```bash -node -v -npm -v -``` - -# Installation {% #installation %} - -{% partial file="mcp-add-ides-tools.md" /%} - -# Usage {% #usage %} - -Once configured, your AI assistant will have access to Appwrite documentation context. You can ask questions like: - -## Example 1: Code generation - -Run the following prompt in your preferred code editor/LLM after enabling the MCP server: - -``` -Show me how to set up real-time subscriptions that trigger on creation of a user -``` - -![Code generation example](/images/docs/mcp/mcp-for-docs/code-generation.avif) - -## Example 2: Troubleshooting - -Run the following prompt in your preferred code editor/LLM after enabling the MCP server: - -``` -I'm getting a 401 error when trying to delete a user. What could be wrong? -``` - -![Troubleshooting example](/images/docs/mcp/mcp-for-docs/troubleshooting.avif) - -## Example 3: Best practices - -Run the following prompt in your preferred code editor/LLM after enabling the MCP server: +The standalone MCP server for Appwrite documentation has been consolidated into the [Appwrite MCP server](/docs/tooling/ai/mcp-servers/api). The unified server exposes the `appwrite_search_docs` tool alongside the Appwrite API tools, so your AI assistant can semantically search the Appwrite documentation and operate on your Appwrite project through a single connection: ``` -What are some of the best security practices for Appwrite Auth in a web app with SSR? +https://mcp.appwrite.io/ ``` -![Best practices example](/images/docs/mcp/mcp-for-docs/best-practices.avif) - -## Example 4: API reference +Once connected, you can ask documentation questions like: -Run the following prompt in your preferred code editor/LLM after enabling the MCP server: - -``` -I want an example of how I can list all users in a Python app -``` +- `Show me how to set up real-time subscriptions that trigger on creation of a user` +- `What are some of the best security practices for Appwrite Auth in a web app with SSR?` +- `I want an example of how I can list all users in a Python app` -![API reference example](/images/docs/mcp/mcp-for-docs/api-reference.avif) \ No newline at end of file +{% arrow_link href="/docs/tooling/ai/mcp-servers/api" %} +Set up the Appwrite MCP server +{% /arrow_link %} diff --git a/src/routes/docs/tooling/ai/vibe-coding/bolt/+page.markdoc b/src/routes/docs/tooling/ai/vibe-coding/bolt/+page.markdoc index 6fdf04a5cc..116d141535 100644 --- a/src/routes/docs/tooling/ai/vibe-coding/bolt/+page.markdoc +++ b/src/routes/docs/tooling/ai/vibe-coding/bolt/+page.markdoc @@ -1,12 +1,14 @@ --- layout: article title: Bolt -description: Learn how to connect the Appwrite docs MCP server to Bolt for AI-assisted development with access to Appwrite documentation. +description: Learn how to connect the Appwrite MCP server to Bolt for AI-assisted development with access to the Appwrite API and documentation. --- -{% section #add-mcp-server step=1 title="Add MCP server" %} +{% section #add-mcp-server step=1 title="Add the MCP server" %} -To connect the Appwrite docs MCP server to Bolt: +Connect the Appwrite MCP server to Bolt for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. + +To add the Appwrite MCP server to Bolt: 1. Go to **Settings** → **Connectors (MCP)**. 2. Click **Custom MCP server**. @@ -19,10 +21,10 @@ To connect the Appwrite docs MCP server to Bolt: {% /only_light %} 3. Enter the following details: - - **Name**: `Appwrite Docs` - - **URL**: `https://mcp-for-docs.appwrite.io` + - **Name**: `Appwrite` + - **URL**: `https://mcp.appwrite.io/` - **Transport Type**: HTTP - - **Authentication**: None + - **Authentication**: MCP OAuth 4. Click **Add MCP server**. {% only_dark %} @@ -32,20 +34,23 @@ To connect the Appwrite docs MCP server to Bolt: ![Bolt add MCP server](/images/docs/mcp/bolt/light/bolt-add-mcp.avif) {% /only_light %} -The Appwrite docs MCP server will now be available in your Bolt projects. +The server uses OAuth for authentication. When Bolt first connects to the server, complete the sign-in flow in your browser to sign in to your Appwrite account and authorize access. + +The Appwrite MCP server will now be available in your Bolt projects. {% /section %} {% section #test-the-integration step=2 title="Test the integration" %} -Once connected, Bolt has access to Appwrite documentation context. You can use prompts like: +Once connected, you can try out the following example prompts: **Example prompts:** +- `Create a new user in my Appwrite project` +- `List all databases in my project` +- `Show me the tables in my database` - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` {% /section %} diff --git a/src/routes/docs/tooling/ai/vibe-coding/claude-desktop/+page.markdoc b/src/routes/docs/tooling/ai/vibe-coding/claude-desktop/+page.markdoc index 6c43913419..7eb8c6f100 100644 --- a/src/routes/docs/tooling/ai/vibe-coding/claude-desktop/+page.markdoc +++ b/src/routes/docs/tooling/ai/vibe-coding/claude-desktop/+page.markdoc @@ -21,25 +21,13 @@ Browse all quick start prompts {% /section %} -{% section #step-2 step=2 title="Add MCP servers" %} +{% section #step-2 step=2 title="Add the MCP server" %} -Connect Appwrite MCP servers to Claude Desktop for deeper integration with the Appwrite API and documentation. +Connect the Appwrite MCP server to Claude Desktop for deeper integration with the Appwrite API and documentation. -Before you begin, ensure you have the following **pre-requisites** installed on your system: +Before you begin, ensure you have [Node.js](https://nodejs.org/en/download) and npm installed on your system. -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} - -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. - -{% /tabsitem %} - -{% tabsitem #docs-server-prerequisites title="Docs server" %} - -[Node.js](https://nodejs.org/en/download) and npm must be installed on your system. - -{% /tabsitem %} -{% /tabs %} +Unlike other IDEs, Claude Desktop only supports local (stdio) MCP servers and not remote servers. The `mcp-remote` package acts as a proxy to connect to the remote Appwrite MCP server. In the Claude Desktop app, open the app's **Settings** page (press `CTRL + ,` on Windows or `CMD + ,` on MacOS) and head to the **Developer** tab. @@ -47,63 +35,23 @@ In the Claude Desktop app, open the app's **Settings** page (press `CTRL + ,` on Clicking on the **Edit Config** button will take you to the `claude_desktop_config.json` file. In case the file is missing, please visit the [Model Context Protocol](https://modelcontextprotocol.io/quickstart/user#2-add-the-filesystem-mcp-server) docs. -Choose which MCP server you want to configure: - -{% tabs %} -{% tabsitem #api-only title="API server" %} - -Add the API server to your configuration: +Add the Appwrite MCP server to your configuration: ```json { "mcpServers": { - "appwrite-api": { - "command": "uvx", + "appwrite": { + "command": "npx", "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_PROJECT_ID": "your-project-id", - "APPWRITE_API_KEY": "your-api-key", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } + "mcp-remote", + "https://mcp.appwrite.io/" + ] } } } ``` -**Configuration:** - -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `nyc`, `fra`) - -{% /tabsitem %} - -{% tabsitem #docs-only title="Docs server" %} - -Add the docs server to your configuration: - -```json -{ - "mcpServers": { - "appwrite-docs": { - "command": "npx", - "args": [ - "mcp-remote", - "https://mcp-for-docs.appwrite.io" - ] - } - } -} -``` - -**Why do we use the `mcp-remote` package?** - -Unlike other IDEs, Claude Desktop only supports local (stdio) MCP servers and not remote servers. The `mcp-remote` package acts as a proxy to connect to the docs MCP server. - -{% /tabsitem %} -{% /tabs %} +The server uses OAuth for authentication. When Claude Desktop first connects to the server, your browser opens so you can sign in to your Appwrite account and authorize access. {% /section %} @@ -111,11 +59,9 @@ Unlike other IDEs, Claude Desktop only supports local (stdio) MCP servers and no Restart the Claude Desktop app, click on the MCP tools button (at the bottom right section of the prompt input) and click on it to view available Appwrite MCP tools. -![Appwrite MCP tools](/images/docs/mcp/claude-desktop/claude-mcp-tools.avif) - -{% info title="uvx ENOENT error" %} +{% info title="npx ENOENT error" %} -In case you see a `uvx ENOENT` error, ensure that you either add `uvx` to the `PATH` environment variable on your system or use the full path to your `uvx` installation in the config file. +In case you see an `npx ENOENT` error, ensure that you either add `npx` to the `PATH` environment variable on your system or use the full path to your `npx` installation in the config file. {% /info %} @@ -123,35 +69,15 @@ In case you see a `uvx ENOENT` error, ensure that you either add `uvx` to the `P {% section #step-4 step=4 title="Test the integration" %} -Try out the following example prompts based on the MCP server you have configured: - -{% tabs %} -{% tabsitem #test-api title="API server" %} +Try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} - -![List users in Appwrite project](/images/docs/mcp/claude-desktop/claude-list-users.avif) {% /section %} diff --git a/src/routes/docs/tooling/ai/vibe-coding/emergent/+page.markdoc b/src/routes/docs/tooling/ai/vibe-coding/emergent/+page.markdoc index e4b66feda8..6837b2fcd6 100644 --- a/src/routes/docs/tooling/ai/vibe-coding/emergent/+page.markdoc +++ b/src/routes/docs/tooling/ai/vibe-coding/emergent/+page.markdoc @@ -1,68 +1,31 @@ --- layout: article title: Emergent -description: Learn how to connect Appwrite MCP servers to Emergent for AI-assisted development with access to the Appwrite API and documentation. +description: Learn how to connect the Appwrite MCP server to Emergent for AI-assisted development with access to the Appwrite API and documentation. --- -{% section #add-mcp-server step=1 title="Add MCP server" %} +{% section #add-mcp-server step=1 title="Add the MCP server" %} -To connect Appwrite MCP servers to Emergent: +To connect the Appwrite MCP server to Emergent: 1. On the homepage, click **Advanced Controls**. 2. Click **Select MCP Tools**. 3. Click **New MCP Server**. -4. Enter a name for your server (e.g., `appwrite` or `appwrite-docs`). -5. Paste one of the following JSON configurations: - -{% tabs %} -{% tabsitem #api-server title="API server" %} - -```json -{ - "mcpServers": { - "appwrite-api": { - "command": "uvx", - "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_PROJECT_ID": "your-project-id", - "APPWRITE_API_KEY": "your-api-key", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } - } - } -} - -``` - -**Configuration:** - -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `fra`, `nyc`) - -{% /tabsitem %} - -{% tabsitem #docs-server title="Docs server" %} +4. Enter a name for your server (e.g., `appwrite`). +5. Paste the following JSON configuration: ```json { "mcpServers": { - "appwrite-docs": { - "command": "npx", - "args": [ - "mcp-remote", - "" - ] + "appwrite": { + "type": "http", + "url": "https://mcp.appwrite.io/" } } } - ``` -{% /tabsitem %} -{% /tabs %} +The server uses OAuth for authentication. When Emergent first connects to the server, complete the sign-in flow in your browser to sign in to your Appwrite account and authorize access. {% /section %} @@ -70,30 +33,13 @@ To connect Appwrite MCP servers to Emergent: Once connected, you can use natural language to interact with Appwrite. Try prompts like: -{% tabs %} -{% tabsitem #test-api title="API server" %} - **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} -{% /tabs %} {% /section %} diff --git a/src/routes/docs/tooling/ai/vibe-coding/lovable/+page.markdoc b/src/routes/docs/tooling/ai/vibe-coding/lovable/+page.markdoc index 160cec2fc7..f2476ea479 100644 --- a/src/routes/docs/tooling/ai/vibe-coding/lovable/+page.markdoc +++ b/src/routes/docs/tooling/ai/vibe-coding/lovable/+page.markdoc @@ -1,35 +1,40 @@ --- layout: article title: Lovable -description: Learn how to connect the Appwrite docs MCP server to Lovable for AI-assisted development with access to Appwrite documentation. +description: Learn how to connect the Appwrite MCP server to Lovable for AI-assisted development with access to the Appwrite API and documentation. --- -{% section #add-mcp-server step=1 title="Add MCP server" %} +{% section #add-mcp-server step=1 title="Add the MCP server" %} -To connect the Appwrite docs MCP server to Lovable: +Connect the Appwrite MCP server to Lovable for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. + +To add the Appwrite MCP server to Lovable: 1. Go to **Settings** → **Connectors** → **Personal connectors**. 2. Click **New MCP server**. 3. Enter the following details: - - **Server name**: `Appwrite Docs` - - **Server URL**: `https://mcp-for-docs.appwrite.io` - - **Authentication**: Select **No authentication** + - **Server name**: `Appwrite` + - **Server URL**: `https://mcp.appwrite.io/` + - **Authentication**: Select **OAuth** 4. Click **Add server**. -The Appwrite docs MCP server will now appear in your list of personal connectors. +The server uses OAuth for authentication. When Lovable first connects to the server, complete the sign-in flow in your browser to sign in to your Appwrite account and authorize access. + +The Appwrite MCP server will now appear in your list of personal connectors. {% /section %} {% section #test-the-integration step=2 title="Test the integration" %} -Once connected, Lovable has access to Appwrite documentation context. You can use prompts like: +Once connected, you can try out the following example prompts: **Example prompts:** +- `Create a new user in my Appwrite project` +- `List all databases in my project` +- `Show me the tables in my database` - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` -{% /section %} \ No newline at end of file +{% /section %} diff --git a/src/routes/docs/tooling/ai/vibe-coding/zenflow/+page.markdoc b/src/routes/docs/tooling/ai/vibe-coding/zenflow/+page.markdoc index 014e4824e7..b88e20fb9b 100644 --- a/src/routes/docs/tooling/ai/vibe-coding/zenflow/+page.markdoc +++ b/src/routes/docs/tooling/ai/vibe-coding/zenflow/+page.markdoc @@ -1,7 +1,7 @@ --- layout: article title: Zenflow -description: Learn how to add the Appwrite MCP servers to agents in Zenflow to interact with both the Appwrite API and documentation. +description: Learn how to add the Appwrite MCP server to agents in Zenflow to interact with both the Appwrite API and documentation. --- {% section #quick-start-prompts step=1 title="Quick start prompts" %} @@ -21,80 +21,26 @@ Browse all quick start prompts {% /section %} -{% section #step-2 step=2 title="Add MCP servers" %} +{% section #step-2 step=2 title="Add the MCP server" %} -Connect Appwrite MCP servers to Zenflow for deeper integration with the Appwrite API and documentation. - -Before you begin, ensure you have the following **pre-requisites** installed on your system: -{% tabs %} -{% tabsitem #api-server-prerequisites title="API server" %} - -[uv](https://docs.astral.sh/uv/getting-started/installation/) must be installed on your system. - -{% /tabsitem %} - -{% tabsitem #docs-server-prerequisites title="Docs server" %} - -[Node.js](https://nodejs.org/en/download) and npm must be installed on your system. - -{% /tabsitem %} -{% /tabs %} +Connect the Appwrite MCP server to Zenflow for deeper integration with the Appwrite API and documentation. It is a remote HTTP server, so there are no additional pre-requisites to install. To add the Appwrite MCP server, open Zenflow and go to the **Settings** > **MCP servers**. From there, select your agent you want to configure MCP for, and then add your custom MCP server. -{% tabs %} -{% tabsitem #api-only title="API server" %} - ```json { "mcpServers": { - "appwrite-api": { - "command": "uvx", - "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_PROJECT_ID": "your-project-id", - "APPWRITE_API_KEY": "your-api-key", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } - } - } -} -``` - -**Configuration:** -- Replace `your-project-id` with your actual Appwrite project ID -- Replace `your-api-key` with your Appwrite API key -- Replace `` with your Appwrite Cloud region (e.g., `nyc`, `fra`) - -{% /tabsitem %} - -{% tabsitem #docs-only title="Docs server" %} - -Update the -```json -{ - "mcpServers": {} -} -``` -to include the docs server: - -```json -{ - "mcpServers": { - "appwrite-docs": { - "url": "https://mcp-for-docs.appwrite.io", + "appwrite": { + "url": "https://mcp.appwrite.io/", "type": "http" } } } ``` -{% /tabsitem %} -{% /tabs %} +The server uses OAuth for authentication. When Zenflow first connects to the server, complete the sign-in flow in your browser to sign in to your Appwrite account and authorize access. -Click **Save**. Once you save the configuration, Zenflow will connect with the MCP server(s) and load all available tools. +Click **Save**. Once you save the configuration, Zenflow will connect with the MCP server and load all available tools. {% /section %} @@ -103,33 +49,14 @@ Click **Save**. Once you save the configuration, Zenflow will connect with the M Open **Zenflow Chat** of your existing task to test your MCP integrations. If you don't have an existing task, you can create one by clicking **New Task**, selecting a task type, and writing a task description. Click **Create and Run**. If you are new to Zenflow, learn more about [how to set up Zenflow](https://docs.zencoder.ai/user-guides/guides/set-up-your-zenflow#step-6:-create-your-first-task). -You can try out the following example prompts based on the MCP server you have configured: - -{% tabs %} -{% tabsitem #test-api title="API server" %} +You can try out the following example prompts: **Example prompts:** - `Create a new user in my Appwrite project` - `List all databases in my project` - `Show me the tables in my database` -- `Create a new row in my table` -- `Delete a specific user by ID` - -{% /tabsitem %} - -{% tabsitem #test-docs title="Docs server" %} - -**Example prompts:** - `How do I set up real-time subscriptions in Appwrite?` - `Show me how to authenticate users with OAuth` -- `What are the best practices for database queries?` - `How do I implement file uploads with Appwrite Storage?` -- `Show me an example of using Appwrite Functions` - -{% /tabsitem %} - -{% /tabs %} - -![Search for portfolio site in Appwrite project](/images/docs/mcp/zenflow/zenflow-chat.avif) {% /section %} diff --git a/src/routes/integrations/mcp-claude/+page.markdoc b/src/routes/integrations/mcp-claude/+page.markdoc index 52c1a92ad7..43eaa29642 100644 --- a/src/routes/integrations/mcp-claude/+page.markdoc +++ b/src/routes/integrations/mcp-claude/+page.markdoc @@ -15,11 +15,8 @@ product: platform: - 'Self-hosted' - 'Cloud' -images: +images: - /images/integrations/mcp-claude/cover.avif - - /images/integrations/mcp-claude/appwrite-api-key.avif - - /images/docs/mcp/claude-desktop/claude-mcp-tools.avif - - /images/docs/mcp/claude-desktop/claude-list-users.avif --- Claude Desktop is a standalone application by Anthropic that allows users to interact with the Claude large language model directly from their Mac or Windows desktops. Designed for convenience and speed, it offers a distraction-free chat experience, supports multiple conversations, and runs natively for faster performance and system integration. Whether you're brainstorming, coding, summarizing documents, or automating workflows, Claude Desktop makes it easy to harness AI assistance without relying on a browser. @@ -34,21 +31,23 @@ This integration enables you to perform various operations on your Appwrite reso To implement the MCP with Claude Desktop integration, there are several steps you must complete: -## Step 1: Create an Appwrite API key +## Step 1: Set up your Appwrite project -First, you must [create an account on Appwrite Cloud](https://cloud.appwrite.io/register) or [self-host Appwrite](https://appwrite.io/docs/advanced/self-hosting) if you haven't already. +First, you must [create an account on Appwrite Cloud](https://cloud.appwrite.io/register) if you haven't already, and create a project. -Select your project (or create a new one), and head to the **Overview** page from the left sidebar. Under the **Integrations** section, click on the **API Keys** tab, and then click on **Create API Key**. Select the scopes for whichever Appwrite services you want to work with, set the duration, and create the API key. You must then copy it for future usage. +The MCP server is a remote server that uses the HTTP transport and OAuth for authentication, so you don't need to create an API key. -![Create API Key](/images/integrations/mcp-claude/appwrite-api-key.avif) +{% info title="Self-hosted Appwrite" %} -Then, head to the **Settings** page from the left sidebar, and copy the **Project ID** and **API Endpoint** for future usage. +The hosted MCP server authenticates against Appwrite Cloud. If you run a [self-hosted Appwrite instance](https://appwrite.io/docs/advanced/self-hosting), follow the [self-hosted setup](/docs/tooling/ai/mcp-servers/api#self-hosted) in the MCP documentation instead. -## Step 2: Configure the MCP server on Cursor +{% /info %} + +## Step 2: Configure the MCP server on Claude Desktop -{% info title="Pre-requisite: Install uv" %} +{% info title="Pre-requisite: Install Node.js" %} -You must install [uv](https://docs.astral.sh/uv/getting-started/installation/) on your system to use the MCP server. +Claude Desktop only supports local (stdio) MCP servers, so the configuration uses the `mcp-remote` package as a proxy to connect to the remote MCP server. You must install [Node.js](https://nodejs.org/en/download) and npm on your system. {% /info %} @@ -58,40 +57,32 @@ To configure the MCP server on Claude Desktop, head to the app's **Settings** pa { "mcpServers": { "appwrite": { - "command": "uvx", + "command": "npx", "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_API_KEY": "", - "APPWRITE_PROJECT_ID": "", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } + "mcp-remote", + "https://mcp.appwrite.io/" + ] } } } ``` -This configuration will set up the MCP server to connect to your Appwrite project using the API key, project ID, and endpoint, which you must update before saving and exiting the file. - -Once you have updated and saved the `claude_desktop_config.json` file, restart Claude Desktop and click on the MCP tools button (at the bottom right section of the prompt input) to view the available MCP tools. - -![Claude MCP Tools](/images/docs/mcp/claude-desktop/claude-mcp-tools.avif) +Once you have updated and saved the `claude_desktop_config.json` file, restart Claude Desktop. When the app first connects to the server, your browser opens so you can sign in to your Appwrite account and authorize access. You can then click on the MCP tools button (at the bottom right section of the prompt input) to view the available MCP tools. {% info title="Claude Code" %} -If you are using the Claude Code CLI, you can use the following command in your terminal to configure the MCP server in the exact same manner: +If you are using the Claude Code CLI, you can use the following command in your terminal to configure the MCP server: ```bash -claude mcp add-json appwrite '{"command":"uvx","args":["mcp-server-appwrite"],"env":{"APPWRITE_PROJECT_ID": "your-project-id", "APPWRITE_API_KEY": "your-api-key", "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1"}}' +claude mcp add --transport http appwrite https://mcp.appwrite.io/ ``` + +Then, run `/mcp` in Claude Code, select **appwrite**, and choose **Authenticate** to sign in to your Appwrite account. {% /info %} ## Step 3: Test the integration Finally, you can test the integration by asking Claude Desktop to list all the users in your Appwrite project. -![Claude Desktop](/images/docs/mcp/claude-desktop/claude-list-users.avif) - # Read more about MCP with Claude Desktop If you would like to learn more about MCP with Claude Desktop, we have some resources that you should visit: diff --git a/src/routes/integrations/mcp-cursor/+page.markdoc b/src/routes/integrations/mcp-cursor/+page.markdoc index de53eb70d7..72628b634d 100644 --- a/src/routes/integrations/mcp-cursor/+page.markdoc +++ b/src/routes/integrations/mcp-cursor/+page.markdoc @@ -15,10 +15,8 @@ product: platform: - 'Self-hosted' - 'Cloud' -images: +images: - /images/integrations/mcp-cursor/cover.avif - - /images/integrations/mcp-cursor/appwrite-api-key.avif - - /images/docs/mcp/cursor/cursor-create-user.avif --- Cursor is an AI-powered code editor built on VS Code, designed to enhance developer workflows with intelligent, context-aware assistance. It offers features like inline code generation, natural language explanations, and project-aware chat, enabling developers to prototype, debug, and refactor code faster with the help of integrated large language models such as Anthropic's Claude 4.0 Sonnet, Google's Gemini 2.5 Pro, and OpenAI's GPT-4.1. @@ -33,47 +31,33 @@ This integration enables you to perform various operations on your Appwrite reso To implement the MCP with Cursor integration, there are several steps you must complete: -## Step 1: Create an Appwrite API key +## Step 1: Set up your Appwrite project -First, you must [create an account on Appwrite Cloud](https://cloud.appwrite.io/register) or [self-host Appwrite](https://appwrite.io/docs/advanced/self-hosting) if you haven't already. +First, you must [create an account on Appwrite Cloud](https://cloud.appwrite.io/register) if you haven't already, and create a project. -Select your project (or create a new one), and head to the **Overview** page from the left sidebar. Under the **Integrations** section, click on the **API Keys** tab, and then click on **Create API Key**. Select the scopes for whichever Appwrite services you want to work with, set the duration, and create the API key. You must then copy it for future usage. +The MCP server is a remote server that uses the HTTP transport and OAuth for authentication, so you don't need to create an API key or install anything on your system. -![Create API Key](/images/integrations/mcp-cursor/appwrite-api-key.avif) +{% info title="Self-hosted Appwrite" %} -Then, head to the **Settings** page from the left sidebar, and copy the **Project ID** and **API Endpoint** for future usage. - -## Step 2: Configure the MCP server on Cursor - -{% info title="Pre-requisite: Install uv" %} - -You must install [uv](https://docs.astral.sh/uv/getting-started/installation/) on your system to use the MCP server. +The hosted MCP server authenticates against Appwrite Cloud. If you run a [self-hosted Appwrite instance](https://appwrite.io/docs/advanced/self-hosting), follow the [self-hosted setup](/docs/tooling/ai/mcp-servers/api#self-hosted) in the MCP documentation instead. {% /info %} +## Step 2: Configure the MCP server on Cursor + To configure the MCP server on Cursor, head to the **Cursor Settings** page, navigate to the **MCP** tab, and click on **Add new global MCP server**. This will open the `mcp.json` file, where you must add the following: ```json { "mcpServers": { "appwrite": { - "command": "uvx", - "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_API_KEY": "", - "APPWRITE_PROJECT_ID": "", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } + "url": "https://mcp.appwrite.io/" } } } ``` -This configuration will set up the MCP server to connect to your Appwrite project using the API key, project ID, and endpoint, which you must update before saving and exiting the file. - -Once you have updated and saved the `mcp.json` file, Cursor will connect with the Appwrite MCP server and load all available tools. You may need to restart Cursor if it is unable to start the MCP server. +Once you have updated and saved the `mcp.json` file, click **Needs login** next to the server in the MCP settings. Your browser opens so you can sign in to your Appwrite account and authorize access. Cursor will then connect with the Appwrite MCP server and load all available tools. ### Skip this step, directly add the server to Cursor @@ -81,26 +65,24 @@ Once you have understood how the Appwrite MCP server is configured in Cursor, yo {% only_light %} {% cards %} -{% cards_item href="https://apwr.dev/api-mcp-cursor?ref=integrations-catalog" title="Add to Cursor" image="/images/docs/mcp/logos/cursor-ai.svg" %} +{% cards_item href="https://cursor.com/install-mcp?name=appwrite&config=eyJ1cmwiOiJodHRwczovL21jcC5hcHB3cml0ZS5pby8ifQ==" title="Add to Cursor" image="/images/docs/mcp/logos/cursor-ai.svg" %} {% /cards_item %} {% /cards %} {% /only_light %} {% only_dark %} {% cards %} -{% cards_item href="https://apwr.dev/api-mcp-cursor?ref=integrations-catalog" title="Add to Cursor" image="/images/docs/mcp/logos/dark/cursor-ai.svg" %} +{% cards_item href="https://cursor.com/install-mcp?name=appwrite&config=eyJ1cmwiOiJodHRwczovL21jcC5hcHB3cml0ZS5pby8ifQ==" title="Add to Cursor" image="/images/docs/mcp/logos/dark/cursor-ai.svg" %} {% /cards_item %} {% /cards %} {% /only_dark %} -This will automatically configure the MCP server, and you will only need to update your Appwrite API key, project ID, and endpoint. +This will automatically configure the MCP server, and you will only need to complete the OAuth sign-in with your Appwrite account. ## Step 3: Test the integration Finally, you can test the integration by asking Cursor Agent to create a new user in your Appwrite project. -![Cursor Agent](/images/docs/mcp/cursor/cursor-create-user.avif) - # Read more about MCP with Cursor If you would like to learn more about MCP with Cursor, we have some resources that you should visit: diff --git a/src/routes/integrations/mcp-windsurf/+page.markdoc b/src/routes/integrations/mcp-windsurf/+page.markdoc index cc5c3f8cd3..9bf8ad00fa 100644 --- a/src/routes/integrations/mcp-windsurf/+page.markdoc +++ b/src/routes/integrations/mcp-windsurf/+page.markdoc @@ -15,10 +15,8 @@ product: platform: - 'Self-hosted' - 'Cloud' -images: +images: - /images/integrations/mcp-windsurf/cover.avif - - /images/integrations/mcp-windsurf/appwrite-api-key.avif - - /images/docs/mcp/windsurf/windsurf-cascade-chat.avif --- Windsurf Editor is a next-gen IDE that embeds a powerful AI agent called Cascade directly into your coding workflow. Unlike tools limited to autocomplete or single-file assistance, Cascade understands your entire project context and can generate code across files, run terminal commands, debug issues, and even deploy applications, all triggered by natural language prompts. With features like Supercomplete, inline AI chat, memories, and live previews, Windsurf aims to keep you in a deep focus state by eliminating context switching and handling repetitive tasks automatically, while still giving you full control over what gets merged or executed. @@ -33,54 +31,38 @@ This integration enables you to perform various operations on your Appwrite reso To implement the MCP with Windsurf Editor integration, there are several steps you must complete: -## Step 1: Create an Appwrite API key +## Step 1: Set up your Appwrite project -First, you must [create an account on Appwrite Cloud](https://cloud.appwrite.io/register) or [self-host Appwrite](https://appwrite.io/docs/advanced/self-hosting) if you haven't already. +First, you must [create an account on Appwrite Cloud](https://cloud.appwrite.io/register) if you haven't already, and create a project. -Select your project (or create a new one), and head to the **Overview** page from the left sidebar. Under the **Integrations** section, click on the **API Keys** tab, and then click on **Create API Key**. Select the scopes for whichever Appwrite services you want to work with, set the duration, and create the API key. You must then copy it for future usage. +The MCP server is a remote server that uses the HTTP transport and OAuth for authentication, so you don't need to create an API key or install anything on your system. -![Create API Key](/images/integrations/mcp-windsurf/appwrite-api-key.avif) +{% info title="Self-hosted Appwrite" %} -Then, head to the **Settings** page from the left sidebar, and copy the **Project ID** and **API Endpoint** for future usage. - -## Step 2: Configure the MCP server on Windsurf Editor - -{% info title="Pre-requisite: Install uv" %} - -You must install [uv](https://docs.astral.sh/uv/getting-started/installation/) on your system to use the MCP server. +The hosted MCP server authenticates against Appwrite Cloud. If you run a [self-hosted Appwrite instance](https://appwrite.io/docs/advanced/self-hosting), follow the [self-hosted setup](/docs/tooling/ai/mcp-servers/api#self-hosted) in the MCP documentation instead. {% /info %} +## Step 2: Configure the MCP server on Windsurf Editor + To configure the MCP server on Windsurf Editor, head to the **Windsurf Editor Settings** page, navigate to the **Model Context Protocol (MCP) Servers** section, and click on **View raw config**. This will open the `mcp_config.json` file, where you must add the following: ```json { "mcpServers": { "appwrite": { - "command": "uvx", - "args": [ - "mcp-server-appwrite" - ], - "env": { - "APPWRITE_API_KEY": "", - "APPWRITE_PROJECT_ID": "", - "APPWRITE_ENDPOINT": "https://.cloud.appwrite.io/v1" - } + "serverUrl": "https://mcp.appwrite.io/" } } } ``` -This configuration will set up the MCP server to connect to your Appwrite project using the API key, project ID, and endpoint, which you must update before saving and exiting the file. - -Once you have updated and saved the `mcp_config.json` file, return to the MCP Servers section in the Windsurf Settings and click on **Refresh**. +Once you have updated and saved the `mcp_config.json` file, return to the MCP Servers section in the Windsurf Settings and click on **Refresh**. When Windsurf first connects to the server, you are prompted to log in, and your browser opens so you can sign in to your Appwrite account and authorize access. ## Step 3: Test the integration Finally, you can test the integration by asking the Cascade chat in the Windsurf Editor to query your database. -![Windsurf Editor Cascade Chat](/images/docs/mcp/windsurf/windsurf-cascade-chat.avif) - # Read more about MCP with Windsurf Editor If you would like to learn more about MCP with Cursor, we have some resources that you should visit: diff --git a/static/images/blog/announcing-remote-appwrite-mcp-server/cover.avif b/static/images/blog/announcing-remote-appwrite-mcp-server/cover.avif new file mode 100644 index 0000000000..efe6a8d719 Binary files /dev/null and b/static/images/blog/announcing-remote-appwrite-mcp-server/cover.avif differ diff --git a/static/images/changelog/2026-07-31.avif b/static/images/changelog/2026-07-31.avif new file mode 100644 index 0000000000..efe6a8d719 Binary files /dev/null and b/static/images/changelog/2026-07-31.avif differ diff --git a/static/images/docs/mcp/antigravity/agent-chat.avif b/static/images/docs/mcp/antigravity/agent-chat.avif deleted file mode 100644 index a74bf3c4fc..0000000000 Binary files a/static/images/docs/mcp/antigravity/agent-chat.avif and /dev/null differ diff --git a/static/images/docs/mcp/bolt/bolt-add-mcp.avif b/static/images/docs/mcp/bolt/bolt-add-mcp.avif index 4b19ea0dfd..c9a9a32a59 100644 Binary files a/static/images/docs/mcp/bolt/bolt-add-mcp.avif and b/static/images/docs/mcp/bolt/bolt-add-mcp.avif differ diff --git a/static/images/docs/mcp/bolt/bolt-mcp-settings.avif b/static/images/docs/mcp/bolt/bolt-mcp-settings.avif index a58a2843ae..d90b1f50fb 100644 Binary files a/static/images/docs/mcp/bolt/bolt-mcp-settings.avif and b/static/images/docs/mcp/bolt/bolt-mcp-settings.avif differ diff --git a/static/images/docs/mcp/bolt/light/bolt-add-mcp.avif b/static/images/docs/mcp/bolt/light/bolt-add-mcp.avif index 47f4435caf..44bdfe0732 100644 Binary files a/static/images/docs/mcp/bolt/light/bolt-add-mcp.avif and b/static/images/docs/mcp/bolt/light/bolt-add-mcp.avif differ diff --git a/static/images/docs/mcp/bolt/light/bolt-mcp-settings.avif b/static/images/docs/mcp/bolt/light/bolt-mcp-settings.avif index a7f4e3cdd8..4767160775 100644 Binary files a/static/images/docs/mcp/bolt/light/bolt-mcp-settings.avif and b/static/images/docs/mcp/bolt/light/bolt-mcp-settings.avif differ diff --git a/static/images/docs/mcp/claude-code/configure-plugin.avif b/static/images/docs/mcp/claude-code/configure-plugin.avif deleted file mode 100644 index 05cfa4d500..0000000000 Binary files a/static/images/docs/mcp/claude-code/configure-plugin.avif and /dev/null differ diff --git a/static/images/docs/mcp/claude-code/implement-file-uploads.avif b/static/images/docs/mcp/claude-code/implement-file-uploads.avif deleted file mode 100644 index 6c903a439f..0000000000 Binary files a/static/images/docs/mcp/claude-code/implement-file-uploads.avif and /dev/null differ diff --git a/static/images/docs/mcp/claude-code/verify-mcp-tools.avif b/static/images/docs/mcp/claude-code/verify-mcp-tools.avif deleted file mode 100644 index 4964dc95bf..0000000000 Binary files a/static/images/docs/mcp/claude-code/verify-mcp-tools.avif and /dev/null differ diff --git a/static/images/docs/mcp/claude-desktop/claude-list-users.avif b/static/images/docs/mcp/claude-desktop/claude-list-users.avif deleted file mode 100644 index 16197d1525..0000000000 Binary files a/static/images/docs/mcp/claude-desktop/claude-list-users.avif and /dev/null differ diff --git a/static/images/docs/mcp/claude-desktop/claude-mcp-tools.avif b/static/images/docs/mcp/claude-desktop/claude-mcp-tools.avif deleted file mode 100644 index dd38e3c502..0000000000 Binary files a/static/images/docs/mcp/claude-desktop/claude-mcp-tools.avif and /dev/null differ diff --git a/static/images/docs/mcp/codex/test-integration.avif b/static/images/docs/mcp/codex/test-integration.avif deleted file mode 100644 index 8f29a531cb..0000000000 Binary files a/static/images/docs/mcp/codex/test-integration.avif and /dev/null differ diff --git a/static/images/docs/mcp/cursor/cursor-create-user.avif b/static/images/docs/mcp/cursor/cursor-create-user.avif deleted file mode 100644 index 2232d5ed72..0000000000 Binary files a/static/images/docs/mcp/cursor/cursor-create-user.avif and /dev/null differ diff --git a/static/images/docs/mcp/logos/dark/grok-build.svg b/static/images/docs/mcp/logos/dark/grok-build.svg new file mode 100644 index 0000000000..e6a54597b0 --- /dev/null +++ b/static/images/docs/mcp/logos/dark/grok-build.svg @@ -0,0 +1 @@ + diff --git a/static/images/docs/mcp/logos/grok-build.svg b/static/images/docs/mcp/logos/grok-build.svg new file mode 100644 index 0000000000..4218747ac1 --- /dev/null +++ b/static/images/docs/mcp/logos/grok-build.svg @@ -0,0 +1 @@ + diff --git a/static/images/docs/mcp/mcp-for-docs/api-reference.avif b/static/images/docs/mcp/mcp-for-docs/api-reference.avif deleted file mode 100644 index 82690c118c..0000000000 Binary files a/static/images/docs/mcp/mcp-for-docs/api-reference.avif and /dev/null differ diff --git a/static/images/docs/mcp/mcp-for-docs/best-practices.avif b/static/images/docs/mcp/mcp-for-docs/best-practices.avif deleted file mode 100644 index a24640490b..0000000000 Binary files a/static/images/docs/mcp/mcp-for-docs/best-practices.avif and /dev/null differ diff --git a/static/images/docs/mcp/mcp-for-docs/code-generation.avif b/static/images/docs/mcp/mcp-for-docs/code-generation.avif deleted file mode 100644 index 93c0699240..0000000000 Binary files a/static/images/docs/mcp/mcp-for-docs/code-generation.avif and /dev/null differ diff --git a/static/images/docs/mcp/mcp-for-docs/troubleshooting.avif b/static/images/docs/mcp/mcp-for-docs/troubleshooting.avif deleted file mode 100644 index 726f1e29b8..0000000000 Binary files a/static/images/docs/mcp/mcp-for-docs/troubleshooting.avif and /dev/null differ diff --git a/static/images/docs/mcp/vscode/copilot-chat.avif b/static/images/docs/mcp/vscode/copilot-chat.avif deleted file mode 100644 index 60b6c7b8f8..0000000000 Binary files a/static/images/docs/mcp/vscode/copilot-chat.avif and /dev/null differ diff --git a/static/images/docs/mcp/windsurf/windsurf-cascade-chat.avif b/static/images/docs/mcp/windsurf/windsurf-cascade-chat.avif deleted file mode 100644 index aca111a2c7..0000000000 Binary files a/static/images/docs/mcp/windsurf/windsurf-cascade-chat.avif and /dev/null differ diff --git a/static/images/docs/mcp/zed/zed-agent-chat.avif b/static/images/docs/mcp/zed/zed-agent-chat.avif deleted file mode 100644 index 28704ce31b..0000000000 Binary files a/static/images/docs/mcp/zed/zed-agent-chat.avif and /dev/null differ diff --git a/static/images/docs/mcp/zenflow/zenflow-chat.avif b/static/images/docs/mcp/zenflow/zenflow-chat.avif deleted file mode 100644 index c34769679b..0000000000 Binary files a/static/images/docs/mcp/zenflow/zenflow-chat.avif and /dev/null differ