Add remote mcp docs + Grok Build docs

.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",

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 %}
 

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.

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.

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.

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.

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://<REGION>.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)