Server providing Argo CD integration for MCP clients.
Gagarin Cloud is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Deploy and operate containers on Gagarin Cloud: services, databases, domains, logs, rollbacks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http gagarin-cloud-mcp https://mcp.gagarin.cloud/mcp
# 2 — ask your agent for something these tools do
# whoami, platform_health, projects and 32 more
Gagarin Cloud costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --transport http gagarin-cloud-mcp https://mcp.gagarin.cloud/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
35 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Which gagarin account this server is acting as, what the credential may do, and the
No parameter schema on file.
The platform\
No parameter schema on file.
Projects this account owns or has been shared with, and the role on each. A
No parameter schema on file.
A project is the unit of naming, access and billing: everything else lives inside one.
No parameter schema on file.
The only call that reads the cluster, and so the only one that can answer
No parameter schema on file.
The Kubernetes manifests, Dockerfiles and connection details for a whole project, so it
No parameter schema on file.
Declares what a service should be. **The image must already be in gagarin\
No parameter schema on file.
Submits a job: an image that runs, exits, and is done — a migration, a backfill, a
No parameter schema on file.
The last 200 lines from a service, or from a job\
No parameter schema on file.
Each recorded revision with its image, port, environment and the dependencies it ran
No parameter schema on file.
Deploys a revision this service already ran. No human approval, because it restores a
No parameter schema on file.
With no domain, hands out gagarin\
No parameter schema on file.
With a domain, releases that custom name. With none, takes the service off the internet
No parameter schema on file.
Its outgoing edges, what depends on it, and how the graph got that way. A private
No parameter schema on file.
Replaces the complete set of things this service may reach. **An empty list disconnects
No parameter schema on file.
Something gagarin runs on your behalf — a database, a cache, a vector store — or an
No parameter schema on file.
The variable names a resource publishes to whatever declares it — and no values.
No parameter schema on file.
The host, port, user, password and URL a client would need. For reading, and for
No parameter schema on file.
New credentials, and everything holding them rolls to pick them up. For an
No parameter schema on file.
Every stored backup of a resource, newest last. Keys are UTC timestamps, so they sort
No parameter schema on file.
A snapshot at this moment, on top of the nightly ones. Rate limited, so do not call it
No parameter schema on file.
Fills a new resource from another one\
No parameter schema on file.
The owner and everyone it has been shared with, plus a pending offer of ownership when
No parameter schema on file.
Grants a role on a project, or changes one somebody already has. An
No parameter schema on file.
Removes somebody from a project. The owner cannot be removed.
No parameter schema on file.
Offers ownership to somebody the project is already shared with. This does not hand it
No parameter schema on file.
Withdraws an offer that has not been accepted, and kills the link in the recipient\
No parameter schema on file.
Balance, burn rate and runway — how long what is running now can keep running. A
No parameter schema on file.
The rows the balance is folded from: metered usage every quarter hour, top-ups, credits
No parameter schema on file.
Every credential, what it may do, when it was last used and when it expires. The one
No parameter schema on file.
Issues a second credential from this one, for a pipeline that has no inbox to approve
No parameter schema on file.
Stops a credential working immediately.
No parameter schema on file.
Answers
No parameter schema on file.
Answers
No parameter schema on file.
Everything in it: every service, every resource, every volume, every backup. Answers
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Gagarin Cloud or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Gagarin Cloud can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.