Using Rivervo from Claude: the MCP connector.
Connect Claude to your Rivervo account and work with your applications in a conversation: status, deploys, logs, metrics and errors, and — if you allow it — deploys, rollbacks, variables and domains.
Rivervo has a connector for Claude (claude.ai, Claude Desktop, the Claude mobile apps and Claude Code). Once it is connected, you can ask Claude about your applications in plain language — «why did the last deploy of shop fail?», «roll back api to the previous version» — and Claude does it through your Rivervo account.
The connector uses the open Model Context Protocol (MCP), so other assistants that support remote MCP servers can connect the same way.
Server address:
https://api.rivervo.com/mcpYou need a Rivervo account with access to at least one application. No API token is needed: you sign in with your Rivervo account, as in the panel.
Connecting from claude.ai, Claude Desktop and mobile
- In Claude, open Settings → Connectors and choose Add custom connector.
- Enter a name (e.g. «Rivervo») and paste the server address
https://api.rivervo.com/mcp. Leave the advanced settings (client ID and secret) empty. - Click Connect. A Rivervo page opens: sign in if you are not signed in yet — with your password, Google, GitHub or Telegram, and two-step sign-in if you use it.
- Check which application is asking for access and where you will be sent afterwards, choose the access level (below) and click Allow.
You are taken back to Claude, and the connector is ready. To use it in a conversation, turn it on in the conversation's tools menu if it is not on already.
A connector added on claude.ai or in Claude Desktop is also available in the Claude mobile apps. In Team and Enterprise organizations, custom connectors may first have to be allowed by an owner of the organization in Claude.
The panel shows the same instructions: Account settings → Connected applications, or How to connect at the bottom of the Applications page.
Connecting from Claude Code
Add the server in your terminal:
claude mcp add --transport http rivervo https://api.rivervo.com/mcpAdd --scope user to make it available in all your projects, not only the current one. Then, in Claude Code, type /mcp, choose rivervo and Authenticate: your browser opens the same Rivervo page, where you choose the access level and click Allow.
Access levels
When you connect, you choose what Claude may do. These are the same levels as for API tokens:
| Access level | What Claude can do |
|---|---|
| Read only | see your applications, deploys and build logs, runtime logs, metrics, usage and spending, and domains; explain errors |
| Read and deploy | everything in Read only, plus deploy, redeploy, roll back and restart applications |
| Full access | everything in Read and deploy, plus environment variables (see and change), connecting and disconnecting domains, and read-only database queries |
Start with Read only if you only want answers; you can connect again with a broader level at any time. If Claude needs more than the level you chose, it tells you so instead of doing it.
Your role still applies
Claude acts on your behalf, with your role in each application: it can only do what you can do yourself in the panel. The access level applies on top of the role.
- Viewer — Claude can read, whatever level you chose.
- Developer — deploys, rollbacks, variables, domains and data, as far as the access level allows.
- Administrator and the account owner — the same as Developer here: everything the connector offers.
If you were given access to applications in other accounts, Claude can work with them too — ask it to list your accounts, or name the account in your request. See Access to an application.
What Claude can do
Look and investigate (Read only):
- list your accounts and applications, and show an application's status and services;
- list deploys and show a deploy with the end of its build log;
- read runtime logs of the site, a worker or the schedule, and search the log history of the last 7 days;
- show metrics (CPU, memory and more) for the last hour, day or week, current usage against the limits, and the expected spending this month;
- list an application's domains and check whether a domain is set up correctly;
- Explain this error for a failed deploy or a crashed service — the same AI explanation as in the panel, within the same daily limit.
Release (Read and deploy):
- deploy the latest commit, or redeploy the running version;
- roll back to a previous version;
- restart an application.
Configure (Full access):
- list environment variables (values are hidden unless you ask to see them), set and remove them — as in the panel, changes reach the application with its next deploy;
- connect a domain (Claude shows the DNS records to create) and disconnect it;
- list the tables of a PostgreSQL or MySQL database, read rows and run read-only queries (
SELECT,SHOW,EXPLAIN).
What Claude cannot do
- Delete anything: applications, services, databases, backups or buckets.
- Make payments, change plans, resources or the spending limit.
- Change data in your databases — queries run read-only.
- Use the terminal or console, or change who has access to an application.
These are done in the panel.
Examples
- «Which of my applications are not running right now?»
- «Why did the last deploy of shop fail? Show the important part of the build log and explain it.»
- «Search the api logs for 500 errors in the last hour.»
- «Deploy shop and tell me when it is live.»
- «Roll back api to the version before the last deploy.»
- «Set FEATURE_CHECKOUT=on for shop and redeploy it.»
- «How many orders were created today? The table is orders.»
Before an action that changes something — a deploy, a rollback, a variable — Claude asks you to confirm it, unless you allowed it to proceed without asking in Claude's settings.
Disconnecting
Account settings → Connected applications lists every assistant connected to your account, with its access level and when it was last used. Disconnect ends its access at once: to use it again, you connect and allow it again.
Removing the connector in Claude only removes it from Claude; to make sure it no longer has access, disconnect it in the panel as well.
Privacy and security
- You sign in on Rivervo's own page; Claude never sees your password. It gets a key that works only with this connector — not with the REST API or the panel — and only with the access level you chose.
- The connection stays active while it is used. If it is not used for 90 days, you will be asked to sign in again.
- Only you can approve a connection: someone signed in to your account on your behalf cannot.
- What Claude reads through the connector — logs, variables you ask to see, rows from your database — becomes part of your conversation with Claude and is handled under Anthropic's terms and privacy policy. Ask for secrets only when you need them.
- Every change made through the connector is a change made with your account, under the same rules and limits as the panel and the REST API.
See also Developer tools for API tokens, the REST API and the rivervo command line.