DEV Community: Aishwari Pahwa

July product update: Remote MCP server, Projects API and more

Aishwari Pahwa — Thu, 06 Aug 2026 07:13:02 +0000

July was all about making Appwrite easier to automate, easier to connect to AI tools, and easier to manage at scale. This month's Appwrite product update covers a hosted remote MCP server, the new Projects API, a simpler CLI login flow built on OAuth Device Authorization, and Appwrite 1.9.6 for self-hosted deployments.

There's a common thread running through all four: removing the manual steps between you and a working project. Setup you used to do by hand, whether that was installing a local server, clicking through Console settings, or pasting credentials into a terminal, is now either automated or gone.

What shipped in Appwrite's July product update?

In July 2026, Appwrite shipped four releases:

Hosted remote Appwrite MCP Server with OAuth. Connect any MCP-compatible AI tool with a single URL, no local install required.
Projects API. Configure and manage nearly every project setting programmatically through the SDKs and CLI.
OAuth Device Authorization for the Appwrite CLI. Log in through your browser instead of typing credentials into the terminal.
Appwrite 1.9.6. Reliability and migration fixes for self-hosted deployments.

Let's dive in.

The Appwrite MCP server is now remote

The Appwrite MCP server is now available as a hosted remote server.

What is the remote Appwrite MCP server?

The remote Appwrite MCP server is a hosted Model Context Protocol endpoint that gives AI coding tools structured access to your Appwrite project and documentation. Because it runs on Appwrite's infrastructure, you add one URL to your AI tool, authenticate with OAuth, and start building.

That means:

No local installation. No cloning, no running a server alongside your editor.
No Python or uv. The previous local setup depended on a Python toolchain. That requirement is gone.
No API keys to generate, paste, or rotate. OAuth handles authorization, so credentials never sit in a config file.

Which AI tools work with it?

The remote server works with any client that supports remote MCP servers, including Claude Code, Cursor, Codex, VS Code, Windsurf, and Zed.

Under the hood, the server keeps the same context-efficient architecture as the local version. That matters more than it sounds: MCP servers that expose hundreds of loosely organized tools eat into a model's context window before it writes a single line of code. Appwrite's server is designed to keep tool definitions lean so the model spends its context on your problem instead of on the catalog.

What can you build with it?

Once connected, your AI tool can read Appwrite documentation directly instead of guessing at SDK signatures from memory, and it can work against your actual project. In practice that means fewer hallucinated method names, fewer round trips to the docs tab, and less time spent correcting code that was written against an older version of the API.

If you were already using the local MCP server, the remote server is the recommended path forward. If you skipped MCP entirely because the setup felt like a side quest, this is the release to revisit.

Read the announcement

Introducing the Projects API

The new Projects API lets you configure and manage nearly every Appwrite project setting through the SDKs and CLI.

What can you automate with the Projects API?

Settings that previously lived only in the Console are now programmable:

Authentication providers. Enable and configure OAuth providers across environments
API keys. Create, scope, and rotate keys as part of a deployment pipeline
Platforms. Register web, Flutter, Apple, and Android platforms
Environment variables. Set project-level variables without manual entry
Email templates. Version your verification, recovery, and invitation templates
Session policies. Control session length and limits per project
Labels. Organize and tag projects at scale

Why does Projects API matter?

Because it turns project configuration into code.

Until now, standing up a new staging environment that matched production meant clicking through the Console and hoping you did not miss a toggle. Configuration drift between development, staging, and production is one of the quieter sources of "it works on my machine" bugs, and it is exactly the problem infrastructure as code was invented to solve.

With the Projects API you can:

Script environment setup. Define a project once and reproduce it on demand.
Version your configuration. Keep project settings in Git alongside your application code, with review and history.
Reproduce configurations across environments. Promote the same settings from development to staging to production instead of recreating them.
Onboard teams faster. New engineers run one command instead of following a Console walkthrough.

It also pairs naturally with the remote MCP server. Configuration that is expressible through an API is configuration an AI agent can reason about and apply for you.

Read the announcement

OAuth Device Authorization for the Appwrite CLI

Logging into the Appwrite CLI is now much simpler.

How does the new CLI login flow work?

Instead of entering credentials in the terminal, the CLI now uses the OAuth 2.0 Device Authorization Grant:

Run the login command in your terminal.
The CLI opens your browser.
Review the permissions being requested and approve access.
The CLI signs in automatically.

You authenticate in your browser, so you never have to type your password into the terminal.

Why device authorization instead of a password prompt?

Device Authorization Grant is the standard OAuth flow for input-constrained clients, which is why you have seen it on smart TVs and streaming devices. Applied to a CLI, it brings a few practical benefits: your identity provider handles authentication, so MFA and SSO come along for the ride; the CLI receives a scoped token rather than your account password; and you get an explicit consent screen showing exactly what access you are granting.

Self-hosted users: nothing breaks. The existing email and password flow continues to work unchanged.

Read the announcement

Appwrite 1.9.6 is now available

Appwrite 1.9.6 focuses on improving reliability for self-hosted deployments following the 1.9.5 release.

What's fixed in Appwrite 1.9.6?

Automatic repair of missing Git provider attributes during migrations. Deployments that hit incomplete Git provider data now self-correct instead of requiring manual intervention.
Migrations are safe to rerun after partial failures. If a migration stops halfway, you can run it again without worrying about compounding the problem. That is a meaningful change if you have ever watched a partial migration and wondered which half completed.
Improved health checks for Appwrite containers and MongoDB. Better signals mean orchestration layers can detect and recover from unhealthy services faster.

If you are self-hosting and still on 1.9.5, this is a recommended upgrade. Review the self-hosting docs before you start, and as always, back up before upgrading.

Read the announcement

Engineering resources

What's to come

July laid the groundwork for what's next, but we're only getting started.

We've been building some of our biggest updates yet, and while we're not quite ready to share them, we think you'll want to keep an eye on what's coming. Stay tuned for major announcements around the Appwrite platform in the weeks ahead.

In the meantime, follow us on X, check the Changelog regularly, and browse the docs to stay up to date with the latest releases.

June product update: React library, Password strength, BAA and more

Aishwari Pahwa — Thu, 30 Jul 2026 10:41:51 +0000

June brought new updates across Appwrite Auth, compliance, React development, and AI-assisted workflows.

This month, we shipped Password strength controls for Auth, self-serve BAA for eligible Pro organizations, the Appwrite React library, and Claude Code marketplace support.

Here is a quick overview of what shipped in June:

Appwrite plugin for Claude Code in the official Claude marketplace
Self-serve BAA for eligible Pro organizations
Password strength controls for Appwrite Auth
Appwrite React library for Auth in React apps

Let’s dive in.

Appwrite plugin for Claude Code is now in the official Claude marketplace

The Appwrite plugin for Claude Code is now listed in the official Claude marketplace.

Developers can now install the plugin directly and start using Claude Code with Appwrite without adding a separate marketplace first.

The plugin includes agent skills for the Appwrite CLI and major SDKs, plus MCP servers for the Appwrite API and documentation. This helps Claude Code better understand Appwrite projects, docs, SDK usage, and common development workflows.

Introducing self-serve BAA

Eligible Pro organizations can now enable a HIPAA Business Associate Agreement directly from the Appwrite Console.

Organization owners can open the Settings tab, select Enable BAA in the BAA section, and accept the agreement from the Console.

This helps teams building healthcare apps, patient portals, telehealth platforms, and PHI-related workflows move faster with the agreement in place.

Read the announcement

Introducing Password strength for Appwrite Auth

Appwrite Auth now lets you enforce Password strength on every project.

You can set a minimum password length and require any combination of an uppercase letter, lowercase letter, number, and special character.

These rules run at sign-up and whenever a user changes their password, so weak passwords are rejected before they land in your project.

Password strength works alongside existing Appwrite Auth protections like password history and the password dictionary, giving teams more control without custom password validation logic.

Read the announcement

Introducing the Appwrite React library

The Appwrite React library helps developers manage Appwrite Auth in React apps with less boilerplate.

It ships with an AppwriteProvider and a small set of authentication hooks for sign-up, sign-in, sign-out, OAuth, and current user state.

The library supports client-side React apps, plus SSR support for Next.js and TanStack Start.

Install it with:

npm install @appwrite.io/react

Read the announcement

Community Recognitions

We are excited to feature Arhan Ansari as part of our monthly Community Recognitions for June 2026. Arhan built HRMate, a cross-platform HR management app built with Expo and Appwrite. It helps companies manage employees, attendance, leave requests, payroll, payslips, and company announcements from one place. Appwrite handles authentication, databases, storage, and realtime updates across the app. Keep in mind that this is a community-backed project and is not maintained by Appwrite.

If you would like to participate in next month's Community Recognitions, join our Discord server and showcase your project.

Engineering resources

What’s next

We are continuing to improve Appwrite across Auth, developer experience, compliance, frontend development, and AI-assisted workflows.

Weekly roundup: Password strength, self-serve BAA, and AI updates

Aishwari Pahwa — Wed, 17 Jun 2026 07:35:01 +0000

This week on the Appwrite blog, we shipped new Auth controls, made BAA acceptance self-serve for Pro organizations, covered Anthropic’s latest Claude models, and shared a full breakdown of everything that landed in May.

Here’s everything that went live this week.

Product announcements

Announcing Password strength

Appwrite Auth now lets you enforce password strength with minimum length and character requirements.

You can set the smallest number of characters a password must have, and require character types such as uppercase letters, lowercase letters, numbers, and special characters.

This gives teams more control over password rules at sign-up and password change, without building custom validation logic from scratch.

Read the announcement: https://appwrite.io/blog/post/announcing-password-strength

Announcing self-serve BAA

Pro organizations can now accept a Business Associate Agreement directly from the Appwrite Console.

Until now, getting a BAA with Appwrite required contacting the team and completing a signing process. With self-serve BAA, eligible Pro organizations can move faster without waiting on a sales or legal cycle.

For teams building healthcare applications that store or process PHI, this removes a major operational blocker from the compliance workflow.

Read the announcement: https://appwrite.io/blog/post/announcing-self-serve-baa

AI and developer ecosystem updates

Anthropic launched Claude Fable 5 and Claude Mythos 5

Anthropic launched Claude Fable 5 and Claude Mythos 5, its first Mythos-class models.

We covered what changed, how the models compare, and what developers should know about benchmarks, safeguards, pricing, and agent workflows.

The post breaks down where these models fit in the current AI developer ecosystem and what they could mean for teams building with coding assistants and agents.

Product updates

May product update

May was packed with releases across Appwrite, including:

→ Presences API

→ Rust runtime

→ Database relationships

→ BigInt columns

→ 7x faster Storage uploads

→ Git deployment triggers

→ Deployment retention

→ Email policies

→ Bun and Deno build runtimes

→ Appwrite plugin for OpenAI Codex

→ Dart 3.12 for Functions and Flutter 3.44 for Sites

From realtime presence to faster Storage uploads and new runtime support, May focused on making Appwrite faster, more flexible, and easier to build with across more stacks.

Read the full update: https://appwrite.io/blog/post/may-product-update-presences-api-rust-runtime-7x-faster-storage-uploads-and-more

Conclusion

We’re continuing to ship product updates, developer tutorials, and AI-focused deep dives every week.

Explore the latest posts on the Appwrite blog to stay updated with everything happening across Appwrite and the developer ecosystem.

May product update: Presences API, Rust runtime, 7x faster Storage uploads, and more

Aishwari Pahwa — Fri, 12 Jun 2026 09:31:26 +0000

Welcome back to the product update.

May was packed with releases across Appwrite. We shipped new tools for realtime collaboration, faster file uploads, better deployment workflows, new runtimes, Auth controls, and database improvements to help you build faster and scale with more confidence.

Here is a quick overview of what we shipped:

Presences API for online, typing, and activity states
Rust runtime for Appwrite Functions
Database relationships are officially out of beta
BigInt columns for Appwrite Databases
Up to 7x faster Storage uploads with parallel chunks
Git deployment triggers for Functions and Sites
Deployment retention for Functions and Sites
Email policies for Appwrite Auth
Bun and Deno build runtimes for Sites
Dart 3.12 for Functions and Flutter 3.44 for Sites
Appwrite plugin for OpenAI Codex

Let’s dive in.

Track who is online, typing, and active with the Presences API

Appwrite now includes a Presences API for short-lived user statuses like online, away, typing, editing, or viewing.

You can use it to build online indicators, typing states, multiplayer presence, collaborative editors, live dashboards, and activity feeds.

Read the announcement

Introducing the Rust runtime for Appwrite Functions

Appwrite Functions now supports Rust as a first-class runtime.

You can write and deploy functions in Rust, pair them with the official Appwrite Rust SDK, and use them for performance-sensitive backend workloads like webhook verification, image processing, payment flows, and data transformation.

Read the announcement

Database relationships are officially out of beta

Database relationships in Appwrite are now production-ready across Appwrite Cloud and self-hosted deployments.

You can model connected data more easily, filter across related records, and build apps with more reliable relationship loading and improved performance.

Read the announcement

Introducing BigInt columns

Appwrite Databases now supports 64-bit signed integers with the new BigInt column type.

BigInt is useful for large counters, external IDs, high-resolution timestamps, financial values, and any data that needs integer precision without floating-point rounding.

Read the announcement

Up to 7x faster Storage uploads with parallel chunks

Appwrite SDKs now upload Storage file chunks in parallel.

In our Node SDK benchmark, a 1.28 GB file upload dropped from 4 minutes 44 seconds to under 40 seconds. That is a 7.10x improvement, with no API changes needed.

Read the announcement

Git deployment triggers for Functions and Sites

Git deployment triggers give you more control over which changes create automatic deployments.

Use branch filters for production, staging, and preview workflows, or path filters so each Function or Site only deploys when relevant files change.

Deployment retention for Functions and Sites

Functions and Sites now support deployment retention.

You can choose how long Appwrite keeps non-active deployments before deleting them automatically. Active deployments are never deleted.

Read the announcement

Email policies for Appwrite Auth

Appwrite Auth now supports email policies.

You can block free providers, aliased emails, disposable inboxes, or enforce provider-specific domains for user creation and email updates.

Bun and Deno build runtimes for Sites

Appwrite Sites now supports Bun and Deno as build runtimes for Node-based frameworks.

You can switch the build runtime per Site from Runtime settings and apply the change on the next deployment.

Read the announcement

Dart 3.12 for Functions and Flutter 3.44 for Sites

Appwrite now supports Dart 3.12 as a Functions runtime and Flutter 3.44 as a build runtime for Sites.

Flutter teams can now build mobile apps, web apps, and backend functions with a more consistent Dart-based workflow.

Read the announcement

Appwrite plugin for OpenAI Codex

The Appwrite plugin is now available for OpenAI Codex.

It includes the Appwrite Docs MCP server and agent skills for the Appwrite CLI, major SDKs, and deployment workflows for Sites and Functions.

Learn more

Community Recognitions

We are excited to feature Ibaraki Douji as part of our monthly Community Recognitions for May 2026. Ibaraki Douji built a full, up-to-date Helm chart for self-hosting Appwrite on Kubernetes that deploys the entire stack, including the API, Console, Realtime, background workers, schedulers, database, Redis, and Kubernetes-native ingress with TLS. It lets you scale each component independently, run clean upgrades, and fits GitOps workflows with tools like ArgoCD and Flux. It has been running in production since Appwrite 1.7.4. Keep in mind that this is a community-backed project and is not maintained by Appwrite.

If you would like to participate in next month's Community Recognitions, join our Discord server and showcase your project.

Engineering Resources

What’s to come

We are continuing to improve Appwrite across realtime collaboration, deployments, performance, databases, Auth, and AI-assisted workflows.

Weekly roundup: Presences API, Git deployment triggers, and AI updates

Aishwari Pahwa — Thu, 11 Jun 2026 12:22:02 +0000

This week on the Appwrite blog, we shipped new product updates, published a hands-on realtime app tutorial, and covered the latest AI developer workflows.

Here’s everything that went live this week.

Product announcements

Announcing the Presences API

Appwrite introduced the Presences API, a new way to track short-lived user statuses like who is online, typing, viewing, or active inside an app.

Presences come with built-in Realtime channels, automatic expiry, and permission-aware subscriptions, making it easier to build collaborative and multiplayer-style experiences without managing temporary state manually.

Read the announcement: https://appwrite.io/blog/post/announcing-presences-api

Announcing Dart 3.12 for Functions and Flutter 3.44 for Sites

Appwrite now supports Dart 3.12 as a Functions runtime and Flutter 3.44 as a build runtime for Sites.

Developers can write serverless functions in Dart, deploy Flutter Web projects with Appwrite Sites, and use Appwrite Cloud for both backend and deployment workflows.

Announcing Git deployment triggers

Git deployment triggers for Appwrite Functions and Sites let developers control which branches and file changes create automatic deployments.

This helps teams build cleaner Git workflows for production branches, staging environments, previews, and monorepos, while avoiding unnecessary builds when unrelated files change.

Read the announcement: https://appwrite.io/blog/post/announcing-git-deployment-triggers

Developer guides

Build a Snapchat clone with Presences and Realtime

We published a hands-on tutorial showing how to build a Snapchat-style app with Appwrite’s Presences API and Realtime.

The guide walks through building realtime features using TanStack Start, TablesDB, Functions, and Storage, covering core experiences like live activity, disappearing content, and presence-driven interactions.

Read the tutorial: https://appwrite.io/blog/post/building-snapchat-clone-with-presences-and-realtime

AI and developer ecosystem updates

Anthropic launched Claude Opus 4.8 with fast mode and dynamic workflows

We covered Claude Opus 4.8 and what it means for developers building with AI agents.

The post breaks down fast mode, dynamic workflows, effort control, pricing, benchmarks, and how these updates point toward more flexible agentic development workflows.

Conclusion

We’re continuing to ship product updates, developer tutorials, and AI-focused deep dives every week.

Explore the latest posts on the Appwrite blog to stay updated with everything happening across Appwrite and the developer ecosystem.

Weekly roundup: Product announcements, AI updates, and developer insights

Aishwari Pahwa — Tue, 26 May 2026 13:13:41 +0000

This week was packed on the Appwrite blog. We shipped major product announcements, covered important AI and developer ecosystem updates, and published new deep dives across backend infrastructure, Auth, Databases, storage, runtime support, AI coding workflows, and modern app development.

Here’s everything that went live this week.

Major product announcements

Faster Appwrite Storage uploads with parallel chunks

We introduced parallel chunk uploads for Appwrite Storage, significantly improving large file upload performance. In benchmark tests, uploads saw improvements of up to 7x faster compared to the previous sequential approach. This update helps reduce upload bottlenecks for modern apps handling large media and datasets.

Read the announcement: https://appwrite.io/blog/post/faster-storage-uploads-parallel-chunks

Email policies for Appwrite Auth

Appwrite Auth now supports Email policies, letting developers block free email providers, aliased addresses, and disposable inboxes directly during signup. Policies can be configured independently through the Console or Server SDKs to improve signup quality and reduce abuse.

Bun and Deno runtimes for Appwrite Sites

Appwrite Sites now supports Bun and Deno build runtimes. Developers can deploy applications using modern JavaScript runtimes without additional infrastructure setup, giving teams more flexibility across frameworks and tooling.

Introducing the Appwrite plugin for Codex

We announced the Appwrite plugin for Codex, which brings Appwrite Skills and MCP support into Codex workflows. The plugin helps AI coding agents understand Appwrite projects, use the right SDK patterns, and build with more accurate context.

Read the announcement: https://appwrite.io/blog/post/announcing-appwrite-codex-plugin

Database relationships are out of beta

Database relationships in Appwrite are now production-ready. After a year of performance improvements, opt-in relationship loading, and full query support, relationships are ready for production workloads across Appwrite Databases.

Announcing BigInt columns

Appwrite Databases now supports BigInt columns, making it easier to store and query large integer values. This is useful for financial data, analytics, IDs, counters, and other workloads where standard integer limits are not enough.

Learn more: https://appwrite.io/blog/post/announcing-bigint-columns

Announcing deployment retention

Deployment retention for Appwrite Functions and Sites lets developers choose how long non-active deployments are kept before they are automatically deleted. This helps teams reduce storage usage and keep deployment history cleaner.

Developer guides and build ideas

3 things you can build with the Rust runtime

We published a practical guide on what developers can build with the Appwrite Rust runtime. The post covers use cases where Rust is a strong fit for server-side workloads, including performance-focused functions and backend processing tasks.

25 startup ideas you can build with vibe coding

We shared 25 startup ideas developers can build with vibe coding, from AI-powered tools to lightweight SaaS products. The post focuses on practical ideas that can move quickly from concept to prototype with the right backend and AI-assisted workflow.

Vibe coding security mistakes to avoid

We published a guide on common security mistakes developers can make when building with AI coding tools. The post covers risks around authentication, secrets, permissions, validation, and dependency management, helping developers move fast without shipping avoidable security issues.

How vibe coding is changing software development

We explored how vibe coding is changing the way developers build software, from faster prototyping to more AI-assisted development workflows. The post looks at what this shift means for developers, teams, and the future of building applications.

Vibe coding vs traditional development

We compared vibe coding with traditional software development, covering how each approach affects speed, control, technical decision-making, debugging, and long-term maintainability. The post helps developers understand where vibe coding works well and where traditional development practices still matter.

Learn more: https://appwrite.io/blog/post/vibe-coding-vs-traditional-development

How to deploy vibe coding projects to production

We published a step-by-step guide on taking vibe-coded apps from prototype to production, covering hosting, domains, secrets, permissions, logs, backups, and pre-launch checks.

How agencies are using vibe coding to ship client projects

We explored how agencies are using vibe coding to prototype faster, reduce delivery timelines, and ship client projects with more structured backend and deployment workflows.

Best backend for vibe coding apps in 2026

We compared backend options for vibe coding apps and looked at how the right backend can reduce complexity across Auth, Databases, Storage, Functions, hosting, and production readiness.

Can vibe coding replace junior developers?

We examined whether vibe coding can replace junior developers and what it actually changes for hiring, learning, code review, debugging, and software development teams.

Best frontend frameworks for vibe coding

We broke down the best frontend frameworks for vibe coding, including how options like Next.js, React, SvelteKit, Nuxt, Vue, Astro, and TanStack Start fit different project needs.

The hidden costs of vibe coding platforms

We covered the hidden costs of vibe coding platforms, including lock-in, fragmented tooling, hosting limits, scaling concerns, and what developers should consider before committing to a platform.

AI deep dives and industry updates

Gemini 3.5 Flash benchmark and capability review

We published a detailed breakdown of Gemini 3.5 Flash, covering benchmark performance, pricing, coding capabilities, reasoning improvements, and how it compares across real-world developer workflows.

Learn more: https://appwrite.io/blog/post/gemini-3-5-flash-deep-dive

OpenAI shipped Codex to the ChatGPT mobile app

We explored what OpenAI’s latest Codex mobile integration means for developers, coding agents, and the future of AI-assisted software workflows directly from mobile devices.

Anthropic launched Claude for Small Business

We covered Anthropic’s new Claude offering for small businesses and what it signals for the growing competition around AI-powered productivity and enterprise tooling.

Learn more: https://appwrite.io/blog/post/anthropic-just-launched-claude-for-small-business

Security and ecosystem updates

The TanStack npm attack shows how fragile modern JavaScript supply chains can be

We broke down the TanStack Start npm supply chain attack and what it means for modern JavaScript teams. The post looks at how dependency risk affects developer workflows and why security needs to be treated as part of the application lifecycle.

Learn more: https://appwrite.io/blog/post/tanstack-start-npm-supply-chain-attack

We’re shipping new product updates, backend improvements, AI deep dives, and developer-focused content every week.

Explore all the latest posts on the Appwrite blog and stay updated with everything happening across Appwrite and the developer ecosystem.

April product update: MongoDB support, Appwrite 1.9.0, Realtime upgrades and AI tooling

Aishwari Pahwa — Mon, 11 May 2026 05:58:38 +0000

Welcome back to the product update. April was packed with major releases across Appwrite. From our official MongoDB partnership and Appwrite 1.9.0 to new infrastructure APIs, Realtime improvements, performance upgrades, and deeper AI integrations, we shipped updates focused on helping you build faster, scale more reliably, and integrate Appwrite more deeply into your workflows.

Here is a quick overview of what we shipped:

Appwrite and MongoDB partnership in Appwrite 1.9.0
Terraform provider for Appwrite
Message based Realtime over a single WebSocket
List response caching with TTL
Introducing the Webhooks API
Official Appwrite Rust Server SDK
Appwrite MCP Server 2.0
Appwrite plugin for Claude Code
Appwrite plugin now available on Cursor

Let's dive in.

Appwrite and MongoDB join forces in Appwrite 1.90

Appwrite and MongoDB are now official partners. Starting with Appwrite 1.9.0, MongoDB is supported as a database option for self hosted deployments.

You can run Appwrite directly on your existing MongoDB infrastructure while keeping the same APIs and SDKs. No breaking changes. No rewrites.

Reuse your existing backups, monitoring, and scaling setup while staying fully open source and self hosted.

This release also includes improvements across Databases, Realtime, Auth, and infrastructure. You get better handling of large integers, new string column types, configurable caching, and improved observability for database usage.

Read the announcement

Terraform provider for Appwrite

You can now manage your Appwrite infrastructure using Terraform.

Define databases, storage, functions, auth, messaging, and more using HCL, and apply changes consistently across environments.

Works with both Appwrite Cloud and self-hosted setups.

Read the announcement

Message-based Realtime over a single WebSocket

Realtime has been reworked to use a message-based protocol over a single persistent WebSocket connection.

You can now manage multiple subscriptions on one connection, update them without reconnecting, and avoid URL length limits entirely. This makes Realtime more predictable and scalable for production workloads.

Learn more

List response caching with TTL

You can now cache list query responses in memory using a configurable TTL.

Repeated reads skip the database entirely until the cache expires, improving performance for feeds, dashboards, and frequently accessed data.

Caching is permission-aware, so users only see data they are allowed to access.

Learn more

Introducing the Webhooks API

Webhooks can now be fully managed through the Appwrite Server SDKs.

Create, update, and delete webhooks directly from code, configure signing secrets, and automate workflows for CI/CD or multi-tenant systems.

Available across all major Server SDKs.

Learn more

Introducing the Appwrite Rust SDK

Appwrite now has an official Server SDK for Rust.

It is async-first, type-safe, and designed for backend services and infrastructure use cases, covering all major Appwrite services. No raw HTTP calls, just a clean and idiomatic Rust API.

Learn more

Appwrite MCP Server 2.0

We have rebuilt the Appwrite MCP server with a simpler architecture.

Instead of passing service flags, everything is now enabled by default. The server exposes two tools: one to search the full Appwrite tool catalog, and one to execute operations. This reduces complexity and uses less of the model’s context.

Read the announcement

Appwrite plugin for Claude Code

Connecting Claude Code to a real backend usually takes manual setup and extra context.

The Appwrite plugin removes that. With a single install, your agent can interact with your Appwrite project using the right context from the start, with built-in skills and MCP servers included.

Learn more

Appwrite plugin now available on Cursor

The Appwrite plugin is now live on the Cursor marketplace.

No need to configure MCP servers or install skills separately. Just install and start building with support for the Appwrite CLI and major SDKs.

Install from the Cursor marketplace

Community Recognitions

We are excited to feature Abid as part of our monthly Community Recognitions for April 2026. Abid created a wrapper around an earlier version of the Appwrite MCP server to reduce token and context usage, an idea that later inspired improvements in Appwrite MCP Server 2.0.

If you would like to participate in next month’s Community Recognitions, join our Discord server and showcase your project.

Engineering Resources

What's to come

We are just getting started with MongoDB and AI integrations. Expect deeper database flexibility, more tools for AI-assisted development, and continued improvements across performance and developer experience.