LoginSign Up
← Back to all sparks
A

Appwrite

DEVOPS
Velocity10.0

Appwrite turns Functions into MCP hosting while quietly putting a meter on Cloud storage.

mcpbackend-as-a-serviceagent-nativecloud-pricingconfig-as-codeself-hosted
◆Current state
Two arcs run in parallel. On the product side, Appwrite is making itself the place AI clients connect to: its own MCP server moved to a hosted endpoint with OAuth on July 31, and a Functions template now lets developers deploy their own MCP servers on Appwrite infrastructure. Alongside that, configuration keeps moving into code through the Projects API, non-destructive CLI column updates and renames, and project targeting without a linked directory. On the business side, Cloud economics are tightening step by step: dev-key creation paused, dormant free projects deleted after 90 days, and build and deployment storage billed from September 1.
◆Where it's heading
Appwrite is repositioning from a backend-as-a-service into an agent-facing platform where the unit of deployment is as likely to be a tool endpoint as a REST route. Every developer-experience release in this window reduces the setup tax on that path: no local MCP install, no API keys to distribute, no directory linking. The commercial moves run in the opposite direction, converting previously unmetered Cloud consumption into billed usage with dated deadlines. Self-hosted releases continue in their own lane, with 1.9.6 repairing the upgrade breakage 1.9.5 introduced.
◆Prediction
Expect the MCP surface to keep expanding, most likely with authentication and scoping controls for user-deployed tool servers, and expect more previously free Cloud allowances to gain enforced limits ahead of the September 1 date. The dev-key deprecation on the same date suggests the two arcs are being sequenced together.

◆Recent moves

  1. 6d ago

    Deploy your own MCP server with the new Functions template

    ⚡ SPARK

    A week after hosting its own MCP server, Appwrite now lets developers deploy theirs on the same infrastructure. This flips the platform's role in the arc from MCP client target to MCP host, and it is the clearest step yet toward Functions being an agent-tool runtime rather than just a serverless endpoint.

    View source ↗
  2. 9d ago

    Pricing update: storage costs for builds and deployments will be enforced

    ⚡ SPARK

    The third step in a stepwise tightening of Cloud economics, after paused dev keys and deleted dormant free projects. Build and deployment artifacts always counted toward storage but were never billed; from September 1 they are, which changes the real cost of a high-deploy-frequency project.

    View source ↗
  3. 9d ago

    Easier project discovery and targeting in the Appwrite CLI

    The CLI can now list projects and organizations for the current session and accept IDs directly, so commands work from any directory without linking one first. It continues the config-as-code arc by making scripted and CI usage the assumed case rather than the awkward one.

    View source ↗
  4. 12d ago

    The Appwrite MCP server is now remote

    ⚡ SPARK

    The MCP server moved from something developers ran locally to a hosted endpoint reached with a URL and a browser OAuth sign-in. It removes the install, the scoped API key and the per-tool configuration that made connecting an AI client to an Appwrite project a setup project of its own.

    View source ↗
  5. 13d ago

    Non-destructive column updates and renames in the Appwrite CLI

    Pushing table changes no longer drops and recreates a column when the API can apply the change in place, so settings like required, default, size, min, max and relationship behaviour update without losing data. Renames work through a previousKey field, which removes the main reason teams avoided declarative schema pushes.

    View source ↗
  6. 20d ago

    Announcing Appwrite 1.9.6 for self-hosted deployments

    A repair release for self-hosted deployments, fixing the upgrade and migration failures the community hit on 1.9.5 with automatic attribute repair, idempotent migrations and more reliable healthchecks. The self-hosted lane keeps moving on its own cadence, separate from the Cloud tightening.

    View source ↗