# Olimpia > Olimpia is a cloud platform from Buenos Aires for running products in production: app hosting, managed Postgres and Redis, and S3-compatible buckets, grouped in projects. Apps are served at https://.olimpia.cc and can use custom domains. It is built to be operated by people from the console (https://olimpia.dev/dashboard) and by AI agents over MCP. ## For agents - MCP server (Streamable HTTP, OAuth 2.1 with PKCE, CIMD and dynamic client registration): https://api.olimpia.dev/mcp - Claude Code: `claude mcp add --transport http olimpia https://api.olimpia.dev/mcp` - Codex: `codex mcp add olimpia --url https://api.olimpia.dev/mcp` - Cursor, VS Code, Windsurf and others: `{"mcpServers": {"olimpia": {"url": "https://api.olimpia.dev/mcp"}}}` - Agent skill and Claude Code plugin: https://github.com/olimpiacloud/olimpia-skills (`bunx skills add olimpiacloud/olimpia-skills`, or `/plugin marketplace add olimpiacloud/olimpia-skills` in Claude Code) - Headless use (CI, scripts): create a personal token in Account → Agents & tokens and send `Authorization: Bearer olimpia_pat_...` to the MCP server or the REST API at https://api.olimpia.dev. ## How deploys work - Sources: code uploaded from a local folder (source=upload, the default for agents), a GitHub repository through the Olimpia GitHub App (redeploys on push), or a public Docker image. - Builds use Railpack, which detects Node, Bun, Deno, Python, Go, Rust, PHP, Ruby, Java, Elixir and static sites; set a Dockerfile path to build with Docker instead. - The app must listen on the `PORT` environment variable (3000 by default). - Upload flow: create_app(source=upload) → upload a .tar.gz of the folder with HTTP PUT to the signed URL → deploy(source_key) → wait until the deployment is `active`. - Environment variables are encrypted and applied on the next deploy. Rollbacks reuse a previous image. ## Data - Postgres 18 and Redis 8 run next to the apps. Apps use the internal URL (`DATABASE_URL`, `REDIS_URL`); public access is optional, over TLS with SNI at `*.db.olimpia.cc` (`sslmode=require` for Postgres, `rediss://` for Redis). - Buckets are S3-compatible (endpoint https://t3.storage.dev, region auto) with credentials scoped to each bucket: `AWS_ENDPOINT_URL_S3`, `AWS_REGION`, `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `BUCKET_NAME`. - Billing is by usage; there are no per-account caps on resources. ## Contact - hola@olimpia.dev