Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"sota": {
"env": {
"SOTA_API_KEY": "sota_your_api_key_here"
},
"args": [
"-y",
"@sota-io/mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for sota.io — deploy web apps via AI agents.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@sota-io/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @sota-io/mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
MCP Server for kubernetes management commands
MCP server for Dynatrace Managed to access logs, events, and metrics.
MCP server for no-payment x402 surface triage, 402 Index health checks, and paid review handoff.
MCP Security Weekly
Get CVE alerts and security updates for io.github.sota-deploy/sota and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for sota.io — deploy web apps via AI agents.
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 your SOTA_API_KEY via env var.sota-mcp-http (Streamable HTTP) — for self-hosting the remote endpoint
that powers mcp.sota.io (used by Claude Desktop and Claude.ai web). Reads
SUPABASE_JWT_SECRET, DATABASE_URL, etc. — most users do not need this;
it's the same code that runs on mcp.sota.io if you want to host your own.Most users want the stdio transport.
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.
No install needed — run directly with npx:
npx -y @sota-io/mcp
Or install globally:
npm install -g @sota-io/mcp
sota-mcp
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"
}
}
}
}
Edit claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"sota": {
"command": "npx",
"args": ["-y", "@sota-io/mcp"],
"env": {
"SOTA_API_KEY": "sota_your_api_key_here"
}
}
}
}
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"
}
}
}
}
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"sota": {
"command": "npx",
"args": ["-y", "@sota-io/mcp"],
"env": {
"SOTA_API_KEY": "sota_your_api_key_here"
}
}
}
}
| 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 |