There is a familiar pause in a useful conversation with an assistant. You’ve found the failed build. You’ve read the logs together. You know which setting needs changing. Then you open another window and do the small, ordinary thing you were just talking about.
We wanted that next step to feel a little more natural.
Watasu MCP now has tools for managing your apps and services, alongside the resources it already uses to understand them. Your assistant can help change configuration, manage domains, capture a backup, query a database, or run a command in a sandbox. You decide what access to give it and which changes you want it to make.
Start with a look around
The connection address is the same:
https://mcp.watasu.io/mcpIf you already use it to ask what happened to a deploy, you can keep doing exactly that. Existing OAuth connections with the read scope stay read-only. The default scope is still read.
When you’re ready to let an assistant make changes, reconnect through a client that requests read write and review the consent screen. You can limit the connection to selected teams. Your normal permissions still apply: access to one app doesn’t open another team’s apps, and a write scope doesn’t make someone a team administrator.
We kept the permission names you already know. Two small words, with a useful choice between them. If you connect with an API key, its scopes apply too: a full-access key can make changes, so choose a restricted key for read-only work.
From “what happened?” to “let’s fix it”
The tools cover the remote operations in the Watasu CLI. That includes apps, configuration, process counts and sizes, private networking, domains, team members, and app access. Managed services get the same treatment: provisioning, attachments, backups, restores, followers, and promotion.
Observability comes along too. An assistant can query runtime logs, metrics, and traces, then use those results to help you understand an issue. You might ask:
Find the errors from the last twenty minutes for the billing app and show me the related trace.
Or, once you’ve decided what to do:
Capture a backup of this database and tell me when it’s ready.
These tools use the same Watasu authorization and product rules as the API. The conversation is another way to work with your account.
Read access can include configuration values, database connection details, and application logs when your account is allowed to read them. That makes the connection useful for real work, and it also means choosing a client you trust. Read-only describes what it can change; it doesn’t mean every result is free of sensitive data.
A terminal when the task needs one
Some questions need a query, or a small experiment.
MCP now supports PostgreSQL commands and Valkey, Redis, and ClickHouse terminal sessions. These require write permission, since a database command can change data. Sessions return a private handle for reading output and sending input. Close one when you’re finished; abandoned sessions expire after fifteen minutes.
For isolated work, an assistant can create or reconnect to a sandbox, run a command, and collect its output and exit code. Your familiar interactive watasu ssh terminal is still there when you want it. Local files, Git remotes, and login credentials stay with the client that owns them.
A little care underneath
We’ve updated the server for the current MCP protocol, including stateless HTTP requests, structured tool results, and clear descriptions of which tools read or change things. Older MCP clients can still use the initialized session flow.
OAuth also supports hosted client metadata documents, alongside the registration flow existing clients use. Fetches verify the destination, reject private addresses, and have time and size limits. We updated the Elixir libraries behind the control plane in the same release.
The Watasu agent plugin has been updated with the new workflows, too. It helps an assistant choose the right tool, understand the connection’s permissions, and handle longer operations without guessing that “accepted” means “finished.”
Give it a small job
Start with a question about an app you know. If read-only access is all you want, you’re already set. If you’d like help carrying out the next step, enable read write and ask for something concrete.
The MCP guide covers setup, permissions, tools, and examples. We’d love to hear what makes this useful in your day, and where it still gets in your way: info@watasu.io.