@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
deploy
Deploy an application to sota.io. Creates a tar.gz archive of the specified directory and uploads it.
"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.
"Show me the build logs for my sota.io project"
set-env
Set an environment variable for a project.
"Set DATABASE_URL on my project to postgres://localhost/mydb"
get-env
List environment variables for a project.
"Show all environment variables for my project"
rollback
Rollback a project to its previous deployment. This swaps the container image without rebuilding.
"Roll back my app to the previous version"
get-status
Get the current deployment status for a project, including URL and recent deployment history.
"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.
"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.
"Delete my sota.io project abc123"
add-domain
Add a custom domain to a project. Returns DNS instructions for pointing the domain.
"Add example.com as a custom domain to my project"
list-domains
List all custom domains for a project.
"Show all custom domains for my project"
get-domain
Get domain details including DNS verification status and SSL state.
"Check the DNS status of my custom domain"
remove-domain
Remove a custom domain from a project.
"Remove the custom domain from my project"
Environment Variables
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