Sota MCP server

Sota is a remote MCP server that gives an AI agent 14 tools, among them add-domain, create-project, create_account. It answers at https://mcp.sota.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.

Status

Answering

Tools

Official

yes, served from sota.io

Reliability

6 of 6 checks

Response time

57 ms

Transport

streamable HTTP

Last checked

24 October 2026

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

Description as the publisher wrote it.

The 14 tools Sota offers

Tool	What it does
`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 subd Inputs: project_id, domain
`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 (po Inputs: name, git_url, git_branch
`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, c Inputs: email, code
`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 av Inputs: project_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 v Inputs: project_id, files, git_url, git_branch, directory
`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', configu Inputs: project_id, domain_id
`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 Inputs: project_id
`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, d Inputs: project_id, deployment_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), d Inputs: project_id
`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. Inputs: project_id
`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-inje
`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. Inputs: project_id, domain_id
`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 ro Inputs: project_id
`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 Postgre Inputs: project_id, key, value

Add Sota to your AI client

Every block below points at https://mcp.sota.io/mcp. Pick your client and copy.

Claude Code: one command in your terminal

claude mcp add --transport http sota https://mcp.sota.io/mcp

Claude Desktop: claude_desktop_config.json

{
  "mcpServers": {
    "sota": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.sota.io/mcp"]
    }
  }
}

Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

{
  "mcpServers": {
    "sota": {
      "url": "https://mcp.sota.io/mcp"
    }
  }
}

VS Code and GitHub Copilot: .vscode/mcp.json

{
  "servers": {
    "sota": {
      "type": "http",
      "url": "https://mcp.sota.io/mcp"
    }
  }
}

Zed: Zed settings.json

{
  "context_servers": {
    "sota": {
      "url": "https://mcp.sota.io/mcp"
    }
  }
}

Windsurf: ~/.codeium/mcp_config.json

{
  "mcpServers": {
    "sota": {
      "serverUrl": "https://mcp.sota.io/mcp"
    }
  }
}

JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON

{
  "mcpServers": {
    "sota": {
      "url": "https://mcp.sota.io/mcp"
    }
  }
}

Continue: .continue/mcpServers/neuronto.yaml

name: Sota
version: 0.0.1
schema: v1
mcpServers:
  - name: Sota
    type: streamable-http
    url: https://mcp.sota.io/mcp

Gemini CLI: ~/.gemini/settings.json

{
  "mcpServers": {
    "sota": {
      "httpUrl": "https://mcp.sota.io/mcp"
    }
  }
}

Codex CLI: MCP server config

{
  "mcpServers": {
    "sota": {
      "type": "http",
      "url": "https://mcp.sota.io/mcp"
    }
  }
}

Warp: MCP servers, + Add, paste JSON

{
  "mcpServers": {
    "sota": {
      "url": "https://mcp.sota.io/mcp"
    }
  }
}

Goose: a one-click extension link

goose://extension?url=https%3A%2F%2Fmcp.sota.io%2Fmcp&type=streamable_http&id=sota&name=Sota

Is Sota up right now?

It answered our last check on 24 October 2026 in 57 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Sota

CustomDomain™0 tools Ansvar: EU Regulations0 tools Fiskmas21 tools Syntitan0 tools microservices.sh0 tools Percher0 tools

Questions about Sota

Is there an official Sota MCP server?

Yes. It is published by sota.io and served from mcp.sota.io, the vendor's own domain: https://mcp.sota.io/mcp.

How many tools does Sota have?

14, as returned by the server's own tools/list on 22 September 2026: add-domain, create-project, create_account, delete-project, deploy, get-domain, get-env, get-logs, and 6 more.

Is Sota down?

It answered our last check on 24 October 2026 in 57 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Sota to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.sota.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Sota need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.sota. Endpoint host: mcp.sota.io. ARD identifier: urn:air:io.sota:mcp:mcp. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.