sota.io
MCP server letting AI assistants deploy and manage sota.io apps and Postgres projects
sota.io is an MCP server for cloud and infrastructure. It can run locally on your machine or as a hosted remote server.
- Platforms
- CLI, API, Web
- Runs
- Locally or Remotely
- Version
- 1.6.0
- Listing updated
Similar MCP servers
Install
Run in a terminal
claude mcp add --transport http mcp https://mcp.sota.io/mcpAdd to Settings → Connectors → Add custom connector
https://mcp.sota.io/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.sota.io/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.sota.io/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"mcp": {
"serverUrl": "https://mcp.sota.io/mcp"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://mcp.sota.io/mcpEnter a Name (for example "sota.io"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://mcp.sota.io/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
About sota.io
The README describes this package as the bridge between an AI client and sota.io, a hosting platform. Instead of switching to a dashboard, you ask your assistant to create a project, push source code, set environment variables, check build logs, or roll back a release, and the server carries out those calls against the sota.io API.
It ships in two forms. The stdio build runs locally via npx and is intended for clients such as Claude Code, Cursor and Windsurf that spawn a local process and read a SOTA_API_KEY from their config. A remote Streamable HTTP endpoint at mcp.sota.io is aimed at Claude Desktop and Claude.ai, authenticated through OAuth. The remote endpoint accepts inline files only, while the local server can also deploy from a directory or a public git URL.
The package suits developers who already work inside an AI coding assistant and want deployment, domains and environment configuration handled in the same conversation. Secret-bearing local env files are excluded from uploads, and runtime secrets are set through the set-env tool.
Tools this server provides (13)
Taken from the project documentation; the running server may differ.
- deploy
- Deploy an app
- get-logs
- Get build/runtime logs
- set-env
- Set environment variable
- get-env
- List environment variables
- rollback
- Rollback to previous deployment
- get-status
- Get deployment status
- list-projects
- List all projects
- create-project
- Create a new project
- delete-project
- Delete a project permanently
- add-domain
- Add custom domain to project
- list-domains
- List custom domains
- get-domain
- Get domain details and DNS status
- remove-domain
- Remove custom domain
What it does
- Deploy from multiple sources
- Deploys inline files, a local directory, or a public git repository, depending on which transport you use.
- Environment variable management
- Lists and sets per-project environment variables that are applied at runtime.
- Build and runtime logs
- Fetches logs for the latest deployment or a specific deployment ID.
- Rollback without rebuild
- Swaps back to the previous container image without rebuilding the app.
- Custom domain setup
- Adds domains, returns DNS instructions, and reports DNS and SSL verification status.
- Two transports
- Offers a local stdio server for IDE clients and a hosted remote endpoint for Claude apps.
Good for
- Deploying a web app from Claude Code or Cursor by asking the assistant to ship it
- Checking build logs after a failed deployment without leaving the editor
- Rolling back a project to its previous version after a bad release
- Attaching a custom domain to a project and checking its DNS status
- Setting or reviewing environment variables such as database URLs for a project
sota.io FAQ
Do I need an API key to use sota.io?
Yes. The README says the stdio server requires SOTA_API_KEY, which is created in the sota.io dashboard settings and must be passed through the MCP client's env block.
Can the hosted endpoint deploy from a git URL?
No. The README states the hosted server accepts only files and rejects directory and git_url; use the local server or the sota CLI for those.
Are my .env files uploaded on deploy?
Local and secret env files such as .env, .env.local and .envrc are never archived. Committed variants like .env.production are kept, and runtime secrets should be set with set-env.
What license is sota.io under?
The README lists the license as MIT.
How do I add sota.io to Claude Code?
Run this command in your terminal: claude mcp add --transport http mcp https://mcp.sota.io/mcp
What are the best alternatives to sota.io?
The closest alternatives to sota.io are awslabs, Komodo MCP Server, VPS MCP & Digital Secretary, DeployMonster and Azure MCP Server.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.
