Gagarin Cloud — Claude Code MCP server: deploy and project memory
One URL gives your agent Gagarin's tools: run the app, add databases, read logs and alerts, keep project memory. Deletes wait for your email approval.
claude mcp add --transport http gagarin https://mcp.gagarin.cloud/mcpWhat Gagarin Cloud does
Point a client at https://mcp.gagarin.cloud/mcp over streamable HTTP and it gets 50 annotated tools. Each one is marked so the client knows which calls need your answer first. Through them an agent runs your app at a live HTTPS address, attaches Postgres, Qdrant, Valkey, a queue or a bucket, wires what may reach what, and rolls back. Alerts, logs, backups and project memory arrive with the same connection, and nothing is deleted until you approve it by email.
Building and pushing an image still needs docker and the source, so that step stays with gg ship on a machine that has both. Everything after it happens here. The server keeps no credential of its own: every call to api.gagarin.cloud carries your bearer token, and the engine's refusals pass through unedited. Holding this server therefore grants nothing by itself, which is what makes a public endpoint in front of a single write gate safe to run.
Sign-in works two ways. With OAuth you hand the client the URL and nothing else; Claude, Claude or ChatGPT open a browser for GitHub or Google. Clients that cannot do OAuth take a credential from gg login or gg creds create in an Authorization: Bearer <your gagarin credential> header. Running npm run stdio from a clone is for developing on the server itself, not a way to install it. An expired or revoked token is caught at the door, because every POST first asks the engine at /v1/whoami and turns its 401 into a 401 with error="invalid_token".
What it helps with
- run an app at a live HTTPS address from inside the agent
- attach Postgres, Qdrant, Valkey, a queue or a bucket to a project
- save a decision or a gotcha into project memory
- check what is already known about a codebase before a new session
- roll back changes without deleting anything unapproved
Example prompts for the agent
- Connect to Gagarin and call
memory_briefingto show what is known about this project. - Deploy the app at a live HTTPS address and give it Postgres.
- Save the auth scheme decision to project memory and link it to the earlier note.
How to install Gagarin Cloud
Platform CLI: remote server
claude mcp add --transport http gagarin https://mcp.gagarin.cloud/mcpPlatform CLI: remote server
codex mcp add gagarin-cloud --url https://mcp.gagarin.cloud/mcpConfig file
{
"mcpServers": {
"gagarin-cloud": {
"url": "https://mcp.gagarin.cloud/mcp"
}
}
}Config file
{
"servers": {
"gagarin-cloud": {
"type": "http",
"url": "https://mcp.gagarin.cloud/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http gagarin-cloud https://mcp.gagarin.cloud/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Gagarin Cloud
How do I install Gagarin Cloud in Claude Code?
Run claude mcp add --transport http gagarin https://mcp.gagarin.cloud/mcp. On connect the client prompts you to sign in with GitHub or Google.
What does Gagarin Cloud do?
It exposes Gagarin's tools to your agent: running the app, databases, a queue or bucket, service connections, rollbacks, plus alerts, logs, backups and project memory.
Do I need a token if my client cannot do OAuth?
Yes. Create a credential with gg login or gg creds create and send it in an Authorization: Bearer <your gagarin credential> header. The server stores no token and forwards yours to the engine.
