appwrite · atharvadeosthale · Oct 8, 2025 · Oct 6, 2025 · Oct 6, 2025 · Oct 6, 2025
diff --git a/src/routes/blog/post/appwrite-compared-to-supabase/+page.markdoc b/src/routes/blog/post/appwrite-compared-to-supabase/+page.markdoc
@@ -10,6 +10,7 @@ category: product
 unlisted: true
 callToAction: true
 ---
+Updated on Oct 6, 2025
 
 If you are looking to build a mobile app, website, tool, or any other application that needs a backend, then you also know the daunting tasks that await. This is probably what brought you to this blog in the first place: looking for a solution to take care of your backend. One of these solutions is a Backend-as-a-Service (BaaS). It provides pre-built backend infrastructure and services to simplify app development, handling server-side tasks like data storage, user management, APIs, server maintenance, security, database management, and more. Two of these solutions are Appwrite and Supabase, and although both are solid options for your BaaS, they’re somewhat different.
 
@@ -162,7 +163,13 @@ Any developer-first product, regardless of how good and simple it may be, will n
 
 # Conclusion
 
-While Appwrite and Supabase are great Backend-as-a-Service (BaaS) offerings that support numerous SDKs, they differ in engineering approaches. The choice between Appwrite and Supabase hinges on your needs and preferences.
+Both Appwrite and Supabase are strong Backend-as-a-Service platforms that make it easier for developers to focus on building instead of managing complex backend systems. They share many similarities but differ in how they approach development.
+
+Supabase offers a familiar experience for developers who prefer working closely with SQL and PostgreSQL. It’s a good choice if you want more control over your database structure, queries, and configurations at the database level.
+
+Appwrite, meanwhile, takes an all-in-one approach. It brings together authentication, databases, storage, functions, real-time features, messaging, and even hosting into a single platform. Whether you use Appwrite Cloud or self-host, you get a consistent and flexible experience that allows you to manage your entire stack in one place.
+
+If you’re looking for a complete, integrated platform to handle everything from your backend to hosting, Appwrite offers a simple and unified solution. But if you prefer the flexibility of direct database control and a more traditional SQL setup, Supabase is a good choice.
 
 Here’s a table that compares both Appwrite and Supabase:
 
@@ -176,13 +183,14 @@ Here’s a table that compares both Appwrite and Supabase:
 | Functions marketplace | Has a marketplace featuring a variety of function templates and integrations such as Discord bots, payments with Stripe, ChatGPT API, etc. | No functions marketplace |
 | Permissions | A simple-to-use permissions system that is consistent across all Appwrite products | Complex permissions system that needs knowledge of SQL to get started |
 | Messaging providers | 10 providers covering SMSes, emails, and push notifications | Zero |
+| Integrated Hosting | Yes | No | 
 
 Here's a price comparison between Appwrite and Supabase to help you choose the one that best suits your needs:
 
 | Feature | Appwrite | Supabase |
 | --- | --- | --- |
 | Pricing Model | Tiered pricing | Tiered pricing |
-| Paid Plan | Starts at $15 per month | Starts at $25 per month |
+| Paid Plan | Starts at $25 per month | Starts at $25 per month |
 
 # Resources
 

diff --git a/src/routes/blog/post/open-source-firebase-alternative/+page.markdoc b/src/routes/blog/post/open-source-firebase-alternative/+page.markdoc
@@ -10,6 +10,8 @@ category: product
 callToAction: true
 ---
 
+Updated on Oct 6, 2025
+
 If you are looking to build a mobile app, website, tool, or any other application that needs a backend, then you also know the daunting tasks that await. This is probably what brought you to this blog in the first place: looking for a solution to take care of your backend. BaaS provides pre-built backend infrastructure and services to simplify app development, handling server-side tasks like data storage, user management, APIs, server maintenance, security, database management, and more. Two of these services are Firebase and Appwrite.
 
 Appwrite and Firebase are both solid options to choose as the Backend-as-a-Service (BaaS) for your app. However, their feature sets can vary substantially. In this article, we will give you a rundown of Appwrite and Firebase to understand how each provider will fit your specific needs.
@@ -141,15 +143,21 @@ Hosting refers to the service that allows developers to deploy and serve web app
 
 # Conclusion
 
-While both Appwrite and Firebase are great Backend-as-a-Service offerings that support numerous SDKs and integrations, they differ in terms of capabilities and pricing. The choice between Appwrite and Firebase hinges on the specific needs of a project. Appwrite stands out with its open-source nature, self-hosting capabilities, pricing affordability, and emphasis on privacy. The community is very welcoming and is praised for it. Firebase's strength lies in its comprehensive ecosystem, Google support, and maturity.
+Both Appwrite and Firebase are powerful Backend-as-a-Service platforms that simplify backend development and help teams focus on building great products rather than managing infrastructure. They share many similarities but take different approaches to solving the same challenges.
+
+Firebase offers a mature, battle-tested ecosystem that’s deeply integrated with Google Cloud. It’s a good choice for teams looking for a managed, ready-to-use solution that scales seamlessly with minimal setup.
+
+Appwrite, meanwhile, brings the benefits of open source to modern development. It provides a unified platform where you can manage authentication, databases, storage, messaging, and even hosting—all in one place. You can self-host Appwrite for full control or use Appwrite Cloud for a managed experience. This flexibility, combined with transparent pricing and a growing developer community, makes Appwrite a strong alternative for teams that want ownership and customization.
+
+Ultimately, the right choice depends on your priorities. If you want a managed, plug-and-play ecosystem with deep Google Cloud integrations, Firebase fits the bill. If you value openness, flexibility, and an all-in-one development experience that you can run anywhere, Appwrite is built for you.
 
 Here’s a table that compares both Appwrite and Firebase:
 
 | Feature                                                                                                                                    | Appwrite                                                                                                                                   | Firebase                                                                                                                                   |
 | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
 | Deployment                                                                                                                                 | Self-hosted or cloud-hosted                                                                                                                | Cloud-hosted only                                                                                                                          |
 | Free plan                                                                                                                                  | Yes, Free plan                                                                                                                             | Yes, Spark plan                                                                                                                            |
-| Paid plan                                                                                                                                  | Yes, Pro plan - $15 per month per member and addons                                                                                        | Yes, Blaze plan - Pay-as-you-go                                                                                                            |
+| Paid plan                                                                                                                                  | Yes, Pro plan - $25 per month                                                                                                              | Yes, Blaze plan - Pay-as-you-go                                                                                                            |
 | Open source                                                                                                                                | Yes                                                                                                                                        | No                                                                                                                                         |
 | Support                                                                                                                                    | Community and email                                                                                                                        | Community, Support Portal, and help center                                                                                                 |
 | Functions marketplace                                                                                                                      | Has a marketplace featuring a variety of function templates and integrations such as Discord bots, payments with Stripe, ChatGPT API, etc. | Has an extensions hub featuring pre-built functions ready to deploy.                                                                       |

diff --git a/src/routes/blog/post/what-is-mcp/+page.markdoc b/src/routes/blog/post/what-is-mcp/+page.markdoc
@@ -11,6 +11,8 @@ featured: false
 callToAction: true
 ---
 
+Updated on Oct 6, 2025
+
 If you've ever tried using an AI assistant for something practical, like pulling real data from your work files, checking a database, or sending a message, then you've probably hit a frustrating wall.
 
 These AI models are brilliant, but they're also **disconnected** from the tools we actually use.
@@ -142,7 +144,11 @@ MCP lets AI assistants **fetch real information** without you needing to switch
 
 Appwrite has introduced the **Appwrite MCP server** to allow AI assistants to interact with Appwrite projects directly. With this, you can now **query databases, fetch user lists, and trigger actions** on your Appwrite project using AI assistants.
 
-# More about Appwrite MCP server
+# More about Appwrite MCP servers
+
+Appwrite now supports two MCP servers that make it easier for AI assistants and developer tools to interact directly with your Appwrite projects and documentation.
+
+# MCP server for Appwrite API
 
 Appwrite MCP is an **MCP server** that connects AI assistants to your **Appwrite project**.
 
@@ -200,12 +206,37 @@ If you get an error that the Appwrite MCP server failed to start, it might be th
 "command": "/Users/username/.local/bin/uvx",
 ```
 
-With the MCP server successfully started on Claude Desktop, you should now be able to ask Claude to retrieve data or perform action on your Appwrite project.
+With the MCP server successfully started on Claude Desktop, you should now be able to ask Claude to retrieve data or perform an action on your Appwrite project.
 
 ![Claude Desktop MCP chat](/images/blog/what-is-mcp/claude-mcp-chat.png)
 
 You can also set up the Appwrite MCP server with other AI tools like Cursor and WindSurf. For more examples and specific setup instructions, check out the [MCP documentation](https://appwrite.io/docs/tooling/mcp?doFollow=true).
 
+# MCP server for Appwrite docs
+
+The Appwrite MCP server for documentation allows AI assistants and code-generation tools to access Appwrite’s complete documentation, making it easier to build, debug, and learn directly through natural language commands.
+
+This means your AI tools can now:
+
+- Access full documentation – AI assistants get direct access to all Appwrite docs.
+- Stay up to date – Responses are based on the latest published documentation.
+- Search intelligently – Use semantic search across documentation for faster, more relevant results.
+- Generate code – Fetch implementation examples and code snippets from the docs.
+- Learn best practices – Get recommendations from Appwrite’s official guidelines.
+
+# Installation
+
+You can integrate the documentation MCP server with multiple tools and editors:
+
+- Claude Desktop
+- Claude Code
+- Cursor
+- Windsurf Editor
+- VS Code
+- OpenCode
+
+For setup instructions and examples, check out the [Appwrite Docs MCP server documentation](/docs/tooling/mcp/docs).
+
 # **Final thoughts**
 
 MCP changes how AI assistants work. Instead of being limited to general knowledge, they can now access **real data from real systems** in a structured way.
@@ -216,5 +247,6 @@ And because MCP is an **open standard**, it doesn't lock anyone into a single pl
 
 # Further reading
 - [Appwrite MCP documentation](/docs/tooling/mcp?doFollow=true)
+- [Appwrite Docs MCP server](/docs/tooling/mcp/docs)
 - [Anthropic MCP documentation](https://docs.anthropic.com/en/docs/agents-and-tools/mcp)
 - [Building a chat app with Appwrite and Google Gemini](/blog/post/build-a-chat-app-with-appwrite-and-gemini?doFollow=true)