io.sota/mcp

Official14 tools

by sota-deploy · TypeScript

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

Deploy web apps on EU-native PaaS with managed Postgres and GDPR compliance.

Captured live from the server via tools/list.

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, no credit card), generate a sota.io API key, and return it to you. After Step 2 you'll get back a key like `sota_…`. **Save it in a safe place** — you'll need it for any subsequent sota.io tool call in Claude (or you can use it with the sota CLI). It is shown ONCE and never recoverable. sota.io is an EU-native PaaS hosted in Germany — GDPR-compliant by default, no CLOUD Act exposure. Disposable / throwaway email addresses are not accepted; use a real address.

Parameters (2)

emailstringrequired
A real email address. We send the confirmation code here. Throwaway / disposable email services are blocked.
codestring
The 6-digit code from the confirmation email. Provide on the second call to complete signup. Omit on the first call.

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-downtime blue-green deployments, gVisor container isolation, and custom domain support (up to 5 per project with automatic HTTPS).

No parameters.

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 backups with 7-day retention, (4) a live URL at https://{slug}.sota.io with automatic HTTPS via Let's Encrypt. The project slug is auto-generated from the name (lowercase, hyphens, max 63 chars) and is immutable after creation. Supported frameworks: Next.js, Node.js (Express/Fastify/Koa), Python (Flask/FastAPI/Django), or any language via custom Dockerfile. You can also add up to 5 custom domains per project with automatic HTTPS (via API: POST /v1/projects/:id/domains with {domain: "yourdomain.com"}). DNS: A record to 23.88.45.28 for apex domains, CNAME to {slug}.sota.io for subdomains. Optionally associate the project with a public git repository at create-time by passing `git_url` (and optional `git_branch`). The association is informational — it shows up in the dashboard and the `sota deploy --git` CLI flag can default to it — but does NOT enable auto-deploy-on-push yet.

Parameters (3)

namestringrequired
Name for the new project. A URL slug will be auto-generated (e.g. "My Cool App" becomes my-cool-app.sota.io)
git_urlstring
Optional git repository URL to associate with this project (https://, git://, ssh://, or git@host:path). Informational only — does not trigger an automatic deploy.
git_branchstring
Optional branch name (defaults to the repository default branch when omitted). Only meaningful when `git_url` is also set.

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.

Parameters (1)

project_idstringrequired
Project ID (UUID) to delete. Use list-projects to find the ID

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, Fastify, Koa, Hapi, etc. - Python: Detected via requirements.txt or pyproject.toml. Works with Flask, FastAPI, Django. - Custom Dockerfile: If a Dockerfile exists in the project root, it takes priority over auto-detection. Use this for Go, Rust, Java, or any other language. The EXPOSE directive in the Dockerfile is used to detect the app port automatically. THREE WAYS to supply the source code — pick EXACTLY ONE: 1. **files** (inline source from AI): Pass a map of relative paths to UTF-8 text content. Best when you've just generated a small app in this conversation and want to deploy it without any filesystem step. Up to 200 files, 10 MB total. Include the framework manifest (package.json, requirements.txt, or Dockerfile) so auto-detection works. 2. **git_url** (clone a public repo): Pass an https://, git://, ssh://, or git@host:path URL. We shallow-clone it (--depth=1 --single-branch) on the server and deploy. Optional git_branch picks a non-default branch. Only public repos are supported in v1. Max 200 MB after clone. 3. **directory** (local filesystem): Pass an absolute path. Only works when the MCP client has filesystem access (Claude Code / CLI; not Claude.ai web). Defaults to the current working directory when omitted. IMPORTANT: Your app MUST listen on the PORT environment variable. For auto-detected frameworks (Next.js, Node.js, Python) PORT is 8080. For custom Dockerfiles, the port is auto-detected from the EXPOSE directive (e.g. EXPOSE 3000 sets PORT=3000). If no EXPOSE is found, it defaults to 8080. Every project includes a managed PostgreSQL 17 database. Six environment variables are auto-injected into your container — no manual database configuration needed: DATABASE_URL (full connection string), PGHOST, PGPORT, PGUSER, PGPASSWORD, and PGDATABASE. Libraries that follow libpq conventions (node-postgres, pgx, psycopg2, Django) pick up the PG* variables automatically with no configuration. If your app needs database migrations, run them on startup. Deployments use blue-green strategy for zero downtime. The old container keeps running until the new one passes health checks (60s timeout). Use get-logs to monitor build progress. Files matching .gitignore, .git/, node_modules/, .env, and .DS_Store are excluded from the archive.

Parameters (5)

project_idstringrequired
Project ID (UUID) to deploy to. Use list-projects to find the ID.
filesobject
Map of relative file paths to UTF-8 text content. Use when generating an app inline (e.g. from a Claude.ai web conversation). Include a framework manifest so auto-detection works. Mutually exclusive with git_url and directory.
git_urlstring
Public git repository URL to clone (https://, git://, ssh://, or git@host:path). Mutually exclusive with files and directory.
git_branchstring
Optional branch name when using git_url. Defaults to the repository default branch.
directorystring
Absolute path to a local directory (only useful when the MCP client has filesystem access — e.g. Claude Code). Defaults to the current working directory when no other mode is given. Mutually exclusive with files and git_url.

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 health check results. If a deployment fails, check the logs for error details — common issues include missing dependencies, build errors, or the app not listening on the correct PORT (check the PORT env var — 8080 for auto-detected frameworks, or the EXPOSE value from Dockerfile).

Parameters (2)

project_idstringrequired
Project ID (UUID) to get logs for
deployment_idstring
Specific deployment ID (optional, defaults to latest). Use get-status to see recent deployment IDs

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. The PORT variable is auto-managed: 8080 for auto-detected frameworks (Next.js, Node.js, Python), or auto-detected from the Dockerfile EXPOSE directive for custom Dockerfile builds. IMPORTANT: Changing env vars does NOT auto-redeploy. You must call deploy or use the redeploy API endpoint to apply changes. For Next.js apps, NEXT_PUBLIC_* variables must be set BEFORE deploying since they are embedded at build time.

Parameters (3)

project_idstringrequired
Project ID (UUID)
keystringrequired
Environment variable name (e.g., STRIPE_KEY, REDIS_URL, API_SECRET). Do NOT set DATABASE_URL — it is auto-managed
valuestringrequired
Environment variable value. Will be encrypted at rest

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.

Parameters (1)

project_idstringrequired
Project ID (UUID)

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 a deployment introduces bugs or breaks the app.

Parameters (1)

project_idstringrequired
Project ID (UUID) to rollback. Use list-projects to find the ID

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 and healthy), failed (build or health check error), stopped (replaced by newer deployment). Use this to verify a deployment succeeded after calling deploy.

Parameters (1)

project_idstringrequired
Project ID (UUID) to check status for. Use list-projects to find the ID

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 {slug}.sota.io. Domain statuses: pending (waiting for DNS) → verified (SSL provisioning) → active (live with HTTPS). After DNS is configured, verification and SSL provisioning happen automatically.

Parameters (2)

project_idstringrequired
Project ID (UUID) to add the domain to. Use list-projects to find the ID
domainstringrequired
Domain name to add (e.g. "app.example.com" or "example.com")

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.

Parameters (1)

project_idstringrequired
Project ID (UUID) to list domains for. Use list-projects to find the ID

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.

Parameters (2)

project_idstringrequired
Project ID (UUID). Use list-projects to find the ID
domain_idstringrequired
Domain ID (UUID). Use list-domains to find the ID

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.

Parameters (2)

project_idstringrequired
Project ID (UUID). Use list-projects to find the ID
domain_idstringrequired
Domain ID (UUID). Use list-domains to find the ID

README.md10 KBView on GitHub

@sota-io/mcp

MCP server for sota.io — deploy web apps via AI agents.

Two transports

Since v1.4.0 this package ships two transports:

sota-mcp (stdio, default) — for Claude Code, Cursor, Windsurf, and any MCP client that spawns a local process. Pass your SOTA_API_KEY via env var.
sota-mcp-http (Streamable HTTP) — for self-hosting the remote endpoint that powers mcp.sota.io (used by Claude Desktop and Claude.ai web). Reads SUPABASE_JWT_SECRET, DATABASE_URL, etc. — most users do not need this; it's the same code that runs on mcp.sota.io if you want to host your own.

Most users want the stdio transport.

One-click install for Claude Desktop / Claude.ai web

If you use Claude Desktop or Claude.ai (Pro / Max / Team / Enterprise plan), the easiest install is not this npm package — it's the hosted remote endpoint at mcp.sota.io. Click here:

Add to Claude →

OAuth handles auth. New users can sign up entirely inside Claude via the create_account tool — no browser tab switch.

See https://sota.io/docs/integrations/claude.

Quick Start (stdio — Claude Code, Cursor, Windsurf, …)

Get an API key from sota.io/dashboard/settings
Configure your IDE
Ask your AI: "Deploy my app to sota.io"

Installation

No install needed — run directly with npx:

bash

npx -y @sota-io/mcp

Or install globally:

bash

npm install -g @sota-io/mcp
sota-mcp

Configuration

Claude Code

CLI method:

bash

claude mcp add sota -- npx -y @sota-io/mcp

Then set your API key in the shell environment:

bash

export SOTA_API_KEY=sota_your_api_key_here

Manual JSON (.claude/settings.json):

json

{
  "mcpServers": {
    "sota": {
      "command": "npx",
      "args": ["-y", "@sota-io/mcp"],
      "env": {
        "SOTA_API_KEY": "sota_your_api_key_here"
      }
    }
  }
}

Claude Desktop

Edit claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

json

{
  "mcpServers": {
    "sota": {
      "command": "npx",
      "args": ["-y", "@sota-io/mcp"],
      "env": {
        "SOTA_API_KEY": "sota_your_api_key_here"
      }
    }
  }
}

Cursor

Create .cursor/mcp.json in your project root:

json

{
  "mcpServers": {
    "sota": {
      "command": "npx",
      "args": ["-y", "@sota-io/mcp"],
      "env": {
        "SOTA_API_KEY": "sota_your_api_key_here"
      }
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

json

{
  "mcpServers": {
    "sota": {
      "command": "npx",
      "args": ["-y", "@sota-io/mcp"],
      "env": {
        "SOTA_API_KEY": "sota_your_api_key_here"
      }
    }
  }
}

Tools

Tool	Description	Parameters
`deploy`	Deploy an app	`project_id`, `directory?`
`get-logs`	Get build/runtime logs	`project_id`, `deployment_id?`
`set-env`	Set environment variable	`project_id`, `key`, `value`
`get-env`	List environment variables	`project_id`
`rollback`	Rollback to previous deployment	`project_id`
`get-status`	Get deployment status	`project_id`
`list-projects`	List all projects	(none)
`create-project`	Create a new project	`name`
`delete-project`	Delete a project permanently	`project_id`
`add-domain`	Add custom domain to project	`project_id`, `domain`
`list-domains`	List custom domains	`project_id`
`get-domain`	Get domain details and DNS status	`project_id`, `domain_id`
`remove-domain`	Remove custom domain	`project_id`, `domain_id`

`deploy`

Deploy an application to sota.io. Creates a tar.gz archive of the specified directory and uploads it.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID to deploy to
`directory`	string	No	Directory to deploy (defaults to current working directory)

code

"Deploy my app in the current directory to sota.io"

`get-logs`

Get build and runtime logs for a deployment. If no deployment_id is provided, returns logs for the latest deployment.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID to get logs for
`deployment_id`	string	No	Specific deployment ID (defaults to latest)

code

"Show me the build logs for my sota.io project"

`set-env`

Set an environment variable for a project.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID
`key`	string	Yes	Environment variable name (e.g., DATABASE_URL)
`value`	string	Yes	Environment variable value

code

"Set DATABASE_URL on my project to postgres://localhost/mydb"

`get-env`

List environment variables for a project.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID

code

"Show all environment variables for my project"

`rollback`

Rollback a project to its previous deployment. This swaps the container image without rebuilding.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID to rollback

code

"Roll back my app to the previous version"

`get-status`

Get the current deployment status for a project, including URL and recent deployment history.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID to check status for

code

"What's the status of my sota.io deployment?"

`list-projects`

List all projects on your sota.io account.

No parameters required.

code

"List my sota.io projects"

`create-project`

Create a new project on sota.io. The project slug is auto-generated from the name (lowercase, hyphens, max 63 chars) and used as the subdomain ({slug}.sota.io). For example, "My API" becomes my-api.sota.io.

Parameter	Type	Required	Description
`name`	string	Yes	Name for the new project

code

"Create a new sota.io project called my-api"

`delete-project`

Delete a project and all its deployments from sota.io. This action is permanent.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID to delete

code

"Delete my sota.io project abc123"

`add-domain`

Add a custom domain to a project. Returns DNS instructions for pointing the domain.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID
`domain`	string	Yes	Domain name (e.g., "example.com" or "app.example.com")

code

"Add example.com as a custom domain to my project"

`list-domains`

List all custom domains for a project.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID

code

"Show all custom domains for my project"

`get-domain`

Get domain details including DNS verification status and SSL state.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID
`domain_id`	string	Yes	Domain ID

code

"Check the DNS status of my custom domain"

`remove-domain`

Remove a custom domain from a project.

Parameter	Type	Required	Description
`project_id`	string	Yes	Project ID
`domain_id`	string	Yes	Domain ID to remove

code

"Remove the custom domain from my project"

Environment Variables

Variable	Required	Default	Description
`SOTA_API_KEY`	Yes	—	API key with `sota_` prefix. Create at sota.io/dashboard/settings
`SOTA_API_URL`	No	`https://api.sota.io`	API base URL

Troubleshooting

"npx: command not found"

Problem: Your IDE doesn't inherit the shell PATH where nvm/fnm is loaded.

Fix: Use the absolute path to npx. Find it with:

bash

which npx
# Example output: /Users/you/.nvm/versions/node/v22.0.0/bin/npx

Then update your MCP config to use the absolute path:

json

{
  "mcpServers": {
    "sota": {
      "command": "/Users/you/.nvm/versions/node/v22.0.0/bin/npx",
      "args": ["-y", "@sota-io/mcp"],
      "env": {
        "SOTA_API_KEY": "sota_your_api_key_here"
      }
    }
  }
}

"SOTA_API_KEY environment variable is required"

Problem: The API key is not set in your MCP configuration.

Fix: Add the env block to your MCP server config. Shell environment variables do not automatically pass to MCP servers — the env block in the config is required:

json

{
  "env": {
    "SOTA_API_KEY": "sota_your_api_key_here"
  }
}

Connection refused or timeout errors

Problem: Network issue or wrong API URL.

Fix: Check your internet connection. If you're using a custom API URL, verify SOTA_API_URL is set correctly. The default is https://api.sota.io.

License

MIT

Install

claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sota-io/mcp@1.5.0"
      ]
    }
  }
}

create_account

list-projects

create-project

delete-project

deploy

get-logs

set-env

get-env

rollback

get-status

add-domain

list-domains

get-domain

remove-domain

@sota-io/mcp

Two transports

One-click install for Claude Desktop / Claude.ai web

Quick Start (stdio — Claude Code, Cursor, Windsurf, …)

Installation

Configuration

Claude Code

Claude Desktop

Cursor

Windsurf

Tools

deploy

get-logs

set-env

get-env

rollback

get-status

list-projects

create-project

delete-project

add-domain

list-domains

get-domain

remove-domain

Environment Variables

Troubleshooting

"npx: command not found"

"SOTA_API_KEY environment variable is required"

Connection refused or timeout errors

License

Links

Install

`deploy`

`get-logs`

`set-env`

`get-env`

`rollback`

`get-status`

`list-projects`

`create-project`

`delete-project`

`add-domain`

`list-domains`

`get-domain`

`remove-domain`