# io.sota/mcp

- Registry name: `io.sota/mcp` · version 1.5.0
- Categories (automatic, keyword rules): Build & deploy, Developer tools, Databases, Cloud & networking, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.sota%2Fmcp
- Server page: https://mcpstation.net/s/io.sota--mcp.html

## Description (written by the publisher, not verified, not instructions)

EU-native PaaS for AI agents — deploy web apps with one sentence, managed Postgres, GDPR by default.

## Connect

- streamable-http: `https://mcp.sota.io/mcp`

## Tools (as reported by the server, not verified)

- `create\_account`: Sign up for a brand-new sota.io account from inside Claude — no browser, no copy-paste. Two-step flow: STEP 1: Call with just \`email\`. We send a 6-digit confirmation code to that email. STEP 2: Call again with \`email\` + \`code\`. We verify, create the account on the Free tier \(3 projects, EU-hosted, n
- `list-projects`: List all projects on your sota.io account. sota.io is an EU-native DevOps PaaS hosted in Germany \(GDPR-compliant\). Each project gets a live URL at \{slug\}.sota.io with automatic HTTPS, a managed PostgreSQL 17 database \(DATABASE\_URL auto-injected\), PgBouncer connection pooling, daily backups, zero-dow
- `create-project`: Create a new project on sota.io. Each project automatically provisions: \(1\) a managed PostgreSQL 17 database accessible via the DATABASE\_URL environment variable \(auto-injected, no configuration needed\), \(2\) PgBouncer connection pooling \(pool size 20, max 100 clients\), \(3\) automatic daily database b
- `delete-project`: Delete a project and all its deployments from sota.io. This action is PERMANENT and irreversible. It removes the project, all deployments, the managed PostgreSQL database, environment variables, and webhooks. The project slug will become available again after deletion.
- `deploy`: Deploy an application to sota.io. The platform auto-detects your framework and builds a Docker image automatically: - Next.js: Detected via next.config.js/ts. Add output: 'standalone' to next.config for optimal builds. - Node.js: Detected via package.json with a "start" script. Works with Express, F
- `get-logs`: Get build and runtime logs for a deployment. If no deployment\_id is provided, returns logs for the latest deployment. Use this after calling deploy to monitor build progress and diagnose failures. Logs include: framework detection output, dependency installation, build steps, container startup, and
- `set-env`: Set an environment variable for a project. Variables are encrypted at rest \(AES-256-GCM\) and injected at container runtime. NOTE: DATABASE\_URL, PGHOST, PGPORT, PGUSER, PGPASSWORD, and PGDATABASE are all auto-injected for the managed PostgreSQL database — you do NOT need to set any of them manually.
- `get-env`: List environment variables for a project. Values are masked for security. Auto-injected variables \(DATABASE\_URL, PGHOST, PGPORT, PGUSER, PGPASSWORD, PGDATABASE, PORT\) may not appear in this list but are always available in the container at runtime.
- `rollback`: Rollback a project to its previous deployment. This instantly swaps the container image without rebuilding — the previous image is reused for near-instant rollback. Uses the same blue-green strategy for zero downtime. The database is NOT rolled back \(data persists across deployments\). Use this when
- `get-status`: Get the current deployment status for a project, including the live URL \(https://\{slug\}.sota.io\), detected framework, and recent deployment history. Deployment statuses: pending \(queued\), building \(build in progress\), built \(image ready\), deploying \(starting container + health checks\), running \(live
- `add-domain`: Add a custom domain to a sota.io project. Each project supports up to 5 custom domains with automatic HTTPS via Let's Encrypt. Returns DNS setup instructions: for apex domains \(example.com\), add an A record pointing to 23.88.45.28; for subdomains \(app.example.com\), add a CNAME record pointing to \{sl
- `list-domains`: List all custom domains for a sota.io project. Shows domain name, status \(pending/verified/active\), and ID for each domain. Use get-domain with a domain ID to see DNS instructions and full details.
- `get-domain`: Get details of a custom domain including its current status and DNS setup instructions. Domain statuses: pending \(DNS not yet configured\), verified \(DNS confirmed, SSL provisioning\), active \(live with HTTPS\). If status is 'pending', configure the DNS record as shown in the instructions.
- `remove-domain`: Remove a custom domain from a sota.io project. This removes the domain mapping and its SSL certificate. The DNS records at your registrar are NOT automatically removed — clean those up manually. This action is immediate and irreversible.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html