Changelog
Keep yourself informed about the most recent additions and improvements
we’ve made to Sevalla.
Sevalla MCP server now has dedicated tools
The Sevalla MCP server no longer runs AI-generated code in a sandbox. The search and execute tools are replaced by 27 dedicated tools that cover everyday workflows directly:
- Discovery - list your services, inspect applications, static sites, and databases, and search the Sevalla docs.
- Deployments - trigger deployments, roll back, and read deployment logs.
- Observability - search runtime and access logs and fetch metrics.
- Configuration - manage environment variables, scale processes, and add custom domains.
- Create - create applications, static sites, and databases.
For everything else in the Sevalla API, such as cloning an application or cancelling a deployment, the generic sevalla_api_* tools find operations by keyword and run them. Reads, creates, updates, and deletes each have their own tool. Every tool is marked as read-only or destructive, so clients like Claude run read-only tools without asking and confirm before destructive actions. Environment variable values are never returned to the agent.
The server also supports the latest MCP protocol version, 2026-07-28, and keeps working with clients on earlier versions. Existing connections keep working, so you don't need to reconnect or change your configuration.
See the full tool list in the MCP docs.
New hostnames and ports for database external connections and TCP proxies
Database external connections and application TCP proxies now have a new hostname and port. Existing ones keep their legacy hostname and port for now, and both work in parallel, so you can move your clients to the new endpoint at any time without downtime. The new connection details are shown in the dashboard:
- Databases - Networking > Public networking > External connection, and Overview > External connection.
- TCP proxies - Networking > Public networking > TCP proxies on your application.
On October 15, 2026, we will disable the legacy hostnames and ports. Your external connections and TCP proxies stay enabled and keep working on the new hostname and port, but clients that still use the legacy ones will no longer be able to connect. Update your applications, database tools, and connection strings to the new hostname and port before then. If you have any issues meeting this deadline, contact our Support team and we'll help you.
If a database or TCP proxy still has a legacy hostname and port, the dashboard shows a warning with the deadline. Open Show legacy details or Show legacy endpoints in the warning to see the old values you need to replace. Nothing changes for internal connections between your Sevalla services.
Read more in the database networking docs and the application networking docs.
Egress IP addresses for applications
You can now see which public IP addresses your application's outbound traffic originates from. Open Networking > Egress IP addresses on any application and allowlist the addresses on external databases and APIs that restrict access by IP.
Applications in Oracle Cloud data centers get a single fixed IP address. Applications in Google Cloud data centers get the IPv4 ranges Google publishes for their region, with a Copy all button to grab the whole list at once.
The same list is available through the API - see Get egress IPs. Read more in the Networking docs.
Preview deployments now build in parallel
Static site pull request previews no longer wait in line behind each other. Previews for different branches now build at the same time, and they run alongside your production deployments instead of queueing behind them. Pushes to the same preview branch still run one after another, so the latest commit on a branch is always the one you end up previewing.
Production deployments are unchanged. They still run one at a time per site, so the most recent deployment is always the one that goes live.
Preview builds also no longer affect your site's status. A failed or in-progress preview will not mark your site as failed or block updates to the site.
Maintenance mode for applications
You can now put an application into maintenance mode from Settings > Maintenance mode. While it is on, every visitor on every domain of the application sees a maintenance page with a 503 status and a Retry-After header instead of your application. The application keeps running and you can still deploy, so it is ideal for database migrations and other planned work.
By default we serve a simple maintenance page. Point Maintenance page URL at any HTTPS page, for example a free Sevalla static site, and we serve that page's content on your own domain instead.
Maintenance mode is also available through the API - see Get maintenance mode and Update maintenance mode. Read more in the Settings docs.