List your agent

sota

MCP server● Hosted · onlineInstallablev1.5.0

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.
All AI agents to automate CI/CD pipelines, ranked →

Similar tools

Listed for the same task: automate CI/CD pipelines

Reviews

No review yet. Used sota? Be the first to help others choose.

What it does

sota is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.

From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installYES
Version1.5.0
Packagesnpm
PriceNot in the registry
First seen26 Sept 2026
Last checked15h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)

Hosted endpoint

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

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

Install package

  • NPM @sota-io/mcp v1.5.0 · runs locally (stdio)

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 2d ago

ONLINE sota answered an MCP connection on 14 Nov 2026 and introduced itself as sota 1.5.0 (MCP protocol 2025-06-18).

14 tools offered to AI assistants

  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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.
Show 2 more
  • 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
  • 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.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Install package@sota-io/mcpDECLAREDSRC-001 Official MCP Registry15h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry15h ago
Version1.5.0DECLAREDSRC-001 Official MCP Registry15h ago
Hosted endpointhttps://mcp.sota.io/mcpDECLAREDSRC-001 Official MCP Registry15h ago
Package registriesnpmDECLAREDSRC-001 Official MCP Registry15h ago
Local install (package)yesDECLAREDSRC-001 Official MCP Registry15h ago
Repositoryhttps://github.com/sota-deploy/mcp-serverDECLAREDSRC-001 Official MCP Registry15h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry15h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry15h ago

Change history

  • CHANGED16 Nov 2026
    remote access: no → yes
  • CHANGED16 Nov 2026
    remote access: yes → no
  • CHANGED09 Nov 2026
    remote access: no → yes
  • CHANGED09 Nov 2026
    remote access: yes → no
  • CHANGED02 Nov 2026
    remote access: no → yes
  • CHANGED02 Nov 2026
    remote access: yes → no
  • CHANGED26 Oct 2026
    remote access: no → yes
  • VERSION26 Oct 2026
    1.1.1 → 1.5.0
  • CHANGED26 Oct 2026
    remote access: yes → no
  • VERSION26 Oct 2026
    1.5.0 → 1.1.1
  • CHANGED19 Oct 2026
    remote access: no → yes
  • VERSION19 Oct 2026
    1.1.1 → 1.5.0
  • CHANGED19 Oct 2026
    remote access: yes → no
  • VERSION19 Oct 2026
    1.5.0 → 1.1.1
  • CHANGED12 Oct 2026
    remote access: no → yes
  • VERSION12 Oct 2026
    1.1.1 → 1.5.0
  • CHANGED12 Oct 2026
    remote access: yes → no
  • VERSION12 Oct 2026
    1.5.0 → 1.1.1
  • CHANGED05 Oct 2026
    remote access: no → yes
  • VERSION05 Oct 2026
    1.1.1 → 1.5.0
  • CHANGED05 Oct 2026
    remote access: yes → no
  • VERSION05 Oct 2026
    1.5.0 → 1.1.1
  • CHANGED28 Sept 2026
    remote access: no → yes
  • VERSION28 Sept 2026
    1.1.1 → 1.5.0
  • CHANGED28 Sept 2026
    remote access: yes → no
  • VERSION28 Sept 2026
    1.5.0 → 1.1.1
  • CHANGED26 Sept 2026
    remote access: no → yes
  • VERSION26 Sept 2026
    1.1.1 → 1.5.0

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run sota? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor sotaLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of sota?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/sota?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/sota/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about sota

How do I connect sota?

Use the hosted endpoint https://mcp.sota.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does sota offer?

When Electra Index connected on 14 Nov 2026, it listed 14 tools: create_account, list-projects, create-project, delete-project, deploy, get-logs, set-env, get-env and more. The full list is in "Live check" above.

Is sota online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.

What can I use sota for?

Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.