Sota.io MCP server
✓ VerifiedLets an AI agent deploy web applications, manage projects, and configure environment variables on a managed PaaS.
Also known as sota-deploy/mcp-server, @sota-io/mcp
- Stars
- 0
- Tools
- 21
- Downloads, 30 days
- —
- Latest version
- 1.5.0
- Last commit
- May 19, 2026
- License
- MIT
What is Sota.io MCP?
Sota.io lets an AI agent deploy web applications, manage projects, and configure environment variables on a managed PaaS. It exposes 21 tools, such as deploy, get-logs, set-env.
Summary generated from the project's README
About Sota.io MCP server
Deploying web applications and managing cloud infrastructure through an AI agent is what this server enables for developers using sota.io. It allows users to handle the entire application lifecycle, from creating new projects and deploying code to managing custom domains and environment variables. By connecting this server to an AI client, you can use natural language to trigger complex deployment workflows or inspect system logs.
For local development environments like Claude Code, Cursor, or Windsurf, you use the stdio transport by providing a SOTA_API_KEY in your configuration. If you prefer using Claude Desktop or the Claude.ai web interface, you can connect via a hosted remote endpoint using OAuth. The server provides specific tools such as deploy, rollback, get-logs, and set-env to interact with your managed PaaS. It also includes domain management capabilities like add-domain and get-domain to handle DNS and SSL status.
What you can do with it
- 1Deploying web applicationsAsk your AI agent to take your local code and push it live to the platform.
- 2Managing project configurationsInstruct an AI to update or view the environment variables for a specific project.
- 3Troubleshooting deployment issuesRequest the build or runtime logs to identify why a deployment might have failed.
- 4Reverting to stable versionsTell the AI to quickly roll back a project to its previous working state.
- 5Configuring custom domainsUse the agent to attach a custom domain and check its DNS verification status.
Written from the project's README. Every use case is checked against a quote from it.
How to install Sota.io MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Sota.io MCP in Claude Code
$ claude mcp add mcp -- npx -y @sota-io/mcpInstall Sota.io MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@sota-io/mcp"
]
}
}
}Install Sota.io MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sota-io/mcp"
]
}
}
}Install Sota.io MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@sota-io/mcp"]}'Install Sota.io MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@sota-io/mcp"
]
}
}
}Install Sota.io MCP in Codex
$ codex mcp add mcp -- npx -y @sota-io/mcpInstall Sota.io MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@sota-io/mcp"]
Install Sota.io MCP in Gemini CLI
$ gemini mcp add -s user mcp npx -- -y @sota-io/mcpInstall Sota.io MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@sota-io/mcp"
]
}
}
}Sota.io MCP tools 21
Detected from the READMEdeployget-logsset-envget-envrollbackget-statuslist-projectscreate-projectdelete-projectadd-domainlist-domainsget-domain
Show all 21 toolsShow fewer tools
remove-domainproject_iddirectorydeployment_idkeyvaluenamedomaindomain_id
Configuration
SOTA_API_KEY
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablesota-deploy/mcp-server is public and reachablegithub.com/sota-deploy/mcp-server ↗Pass
- Package names this repository as its source@sota-io/mcp names sota-deploy/mcp-server as sourcenpmjs.com/package/@sota-io/mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-05-19github.com/sota-deploy/mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @sota-io/mcpPass
- No critical advisory in the package or its dependencies144 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model21 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 1272 msPass
README
View 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 yourSOTA_API_KEYvia env var.sota-mcp-http(Streamable HTTP) — for self-hosting the remote endpoint that powersmcp.sota.io(used by Claude Desktop and Claude.ai web). ReadsSUPABASE_JWT_SECRET,DATABASE_URL, etc. — most users do not need this; it's the same code that runs onmcp.sota.ioif 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:
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:
npx -y @sota-io/mcp
Or install globally:
npm install -g @sota-io/mcp
sota-mcp
Configuration
Claude Code
CLI method:
claude mcp add sota -- npx -y @sota-io/mcp
Then set your API key in the shell environment:
export SOTA_API_KEY=sota_your_api_key_here
Manual JSON (.claude/settings.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
{
"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:
{
"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:
{
"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) |
"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) |
"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 |
"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 |
"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 |
"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 |
"What's the status of my sota.io deployment?"
list-projects
List all projects on your sota.io account.
No parameters required.
"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 |
"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 |
"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") |
"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 |
"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 |
"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 |
"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:
which npx
# Example output: /Users/you/.nvm/versions/node/v22.0.0/bin/npx
Then update your MCP config to use the absolute path:
{
"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:
{
"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
Links
Sota.io MCP questions
How do I add Sota.io MCP to Claude Code?
Run claude mcp add mcp -- npx -y @sota-io/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Sota.io MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Sota.io MCP provide?
It exposes 21 tools, including deploy, get-logs, set-env, get-env, rollback.
How do I deploy an app using Sota?
You can deploy an application by asking your AI to "Deploy my app to sota.io" or using the deploy tool with a project ID and directory.
Can I use Sota with Claude Desktop?
Yes, you can install it via the hosted remote endpoint at mcp.sota.io or by configuring your local claude_desktop_config.json with your SOTA_API_KEY.
What should I do if I get an 'npx: command not found' error?
This usually happens because your IDE doesn't inherit your shell PATH. You should find the absolute path to npx using 'which npx' and use that in your MCP configuration.