Pocketnook vs Sota
A side-by-side look at the Pocketnook and Sota MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Pocketnook for cloud platforms work as a local process; choose Sota for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Pocketnook when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
POCKETNOOK_TOKEN. - You want tools like
deploy, deploy_directory, list_nooks.
Choose Sota when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SOTA_API_KEY, SOTA_API_URL. - You want tools like
deploy, get-logs, set-env.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 51/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | POCKETNOOK_TOKEN | SOTA_API_KEYSOTA_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 13 |
| Full listing | View Pocketnook | View Sota |
Tools & capabilities
Pocketnook tools 5
deployDeploy a GitHub repository — the tip of its default branch — and return its private URL.deploy_directoryDeploy a directory from this machine as it is on disk. No repository needed.list_nooksEverything this account has deployed, with URLs and status.nook_logsBuild output — the first thing to read when a deploy went wrong.stop_nookTake a nook offline, keeping its URL, grants, and secrets.
Sota tools 13
deployDeploy an appget-logsGet build/runtime logsset-envSet environment variableget-envList environment variablesrollbackRollback to previous deploymentget-statusGet deployment statuslist-projectsList all projectscreate-projectCreate a new projectdelete-projectDelete a project permanentlyadd-domainAdd custom domain to projectlist-domainsList custom domainsget-domainGet domain details and DNS status- +1 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Pocketnook
{
"mcpServers": {
"pocketnook": {
"command": "npx",
"args": [
"-y",
"@pocketnook/mcp"
],
"env": {
"POCKETNOOK_TOKEN": "YOUR_POCKETNOOK_TOKEN_HERE"
}
}
}
}
Sota
{
"mcpServers": {
"sota": {
"command": "npx",
"args": [
"-y",
"@sota-io/mcp"
],
"env": {
"SOTA_API_KEY": "YOUR_SOTA_API_KEY_HERE",
"SOTA_API_URL": "YOUR_SOTA_API_URL_HERE"
}
}
}
}
Frequently asked questions
Pocketnook is categorized under Cloud Platforms and uses a local stdio subprocess. Sota belongs to Cloud Platforms and uses a local stdio subprocess. Pick Pocketnook for cloud platforms work and Sota for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Pocketnook has no declared pricing — check the project's own site. Sota has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add pocketnook and sota as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pocketnook has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Sota has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.