u/HappyStark1234

https://preview.redd.it/87m9ov7d5wjh1.png?width=1280&format=png&auto=webp&s=2e94080755d38901e95bea3a07137036e08b61e2

Hey everyone,

We’ve just added support for custom MFA factors in Appwrite Authentication.

You can now build custom MFA delivery flows using channels such as WhatsApp, voice calls, Telegram, or your own messaging system.

Appwrite handles generating and verifying the verification code, while your Function handles delivering it through the channel you choose.

This gives you more flexibility to build an MFA flow around your users and your existing communication infrastructure.

You can learn more and see how to set it up in the guide: https://appwrite.io/blog/post/custom-mfa-factor

What custom MFA channels would you like to use with Appwrite?

https://preview.redd.it/dj1zyrhhx4jh1.png?width=1280&format=png&auto=webp&s=2a4a099954e3c426d927dcf14ae2bb6c49fbf5cd

We’ve made another improvement to make builds on Appwrite faster.

Appwrite now caches your dependencies between builds, so you don’t have to download the same packages again every time you deploy.

In our tests with a real-world Next.js app, pnpm installs went from 11.7s to 2.8s, while bun went from 9.6s to 2.3s.

The cache works automatically, with no configuration needed.

Want to know how we got the install times down? We went into the details of how the cache works, why we chose SquashFS, and what happens during a build.

Read the full deep dive and let us know what you think: https://appwrite.io/blog/post/inside-appwrites-new-build-cache

https://preview.redd.it/biu2gusm1yih1.png?width=1280&format=png&auto=webp&s=e3069d5e4eee067614251f41f93d60cd3bc59d94

Hey everyone,

We’ve made an under-the-hood change to Appwrite Sites that should make a noticeable difference for larger deployments.

New Sites and Functions deployments on Appwrite Cloud now use SquashFS, allowing Appwrite to mount deployments directly instead of extracting everything before serving a cold deployment.

In production, this made cold starts up to 51% faster for larger deployments, with 50 MB deployments seeing a 42% improvement, 100 MB seeing 39%, 200 MB seeing 51%, and 800 MB seeing 38%.

Your existing setup stays the same. Just redeploy an existing Site to get the new deployment format.

Here's the full breakdown: https://appwrite.io/blog/post/appwrite-sites-squashfs-migration

If you’re running larger Sites, we’d love to hear how it goes.

https://preview.redd.it/ifg3li7rnwih1.png?width=1280&format=png&auto=webp&s=7c4e123b6904811f72f629dfd8c9d7e9b731cbf0

Hey everyone,

The Appwrite CLI is now rewritten in Go.

We rewrote it from TypeScript to make it faster and lighter, while keeping the experience you already know.

Startup is now up to 22× faster, npm dependencies went from 330 to 2, the binary went from 66 MB to around 14 MB, and memory usage during deployment dropped from 283.5 MB to 28 MB.

Your existing commands, configuration, and workflows continue to work as before.

We shared the full story behind the rewrite, including what we measured, why we chose Go, and how we kept the new CLI compatible.

If you’ve been using the CLI, give the new version a try and let us know how it feels.

Read the announcement: https://appwrite.io/blog/post/rewriting-the-appwrite-cli-in-go

https://preview.redd.it/hv584ye6hiih1.png?width=1280&format=png&auto=webp&s=223104b43a82b7aab242aa110e7d37ef6bd4c904

Hey everyone,

We've added a new MCP server template to Appwrite Functions.

Building an MCP server is usually the easy part. Hosting one is where things get complicated. With the new template, you can deploy a working, stateless MCP server over HTTPS using the official MCP Python SDK. Your Function's domain becomes your MCP server URL, making it easy to connect with Claude Code, Cursor, Claude Desktop, and other MCP clients.

The template includes demo tools to help you get started, optional bearer authentication, automatic deployments, and dynamic Appwrite API keys so your tools can securely access your Appwrite project. Right now it's designed for Python-based, stateless MCP servers, so it's a good fit for tools that don't need to maintain server-side session state.

Read the full announcement: https://appwrite.io/blog/post/announcing-mcp-server-template

We'd love to see what you build with it.

https://preview.redd.it/zywfo4bqalhh1.png?width=1280&format=png&auto=webp&s=64bb75fae090f00770f69e6a4c410a0ffc1c48a2

Hey everyone,

We've made the Appwrite MCP server a hosted remote server.

Instead of running a local MCP server and managing API keys, you can now connect your AI tool with a single URL and sign in securely with OAuth.

With OAuth, you can review the requested permissions, choose exactly which scopes to grant, access console-level Appwrite APIs that weren't available with API key authentication, and revoke access tokens at any time from your Appwrite account.

The remote server also includes built-in Appwrite documentation search, so one connection gives your AI access to both your Appwrite project and the docs.

If you're self-hosting Appwrite, the local MCP server with API key authentication continues to be fully supported.

Read the full announcement: https://appwrite.io/blog/post/announcing-remote-appwrite-mcp-server

Let us know what you think or what you'd like to see next.