A side-by-side look at the Pocketnook and Shipvela 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 Shipvela for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
POCKETNOOK_TOKEN.deploy, deploy_directory, list_nooks.Rows where the two servers differ are marked.
| Spec | S Shipvela | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 51/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | POCKETNOOK_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Pocketnook | View Shipvela |
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.No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"pocketnook": {
"command": "npx",
"args": [
"-y",
"@pocketnook/mcp"
],
"env": {
"POCKETNOOK_TOKEN": "YOUR_POCKETNOOK_TOKEN_HERE"
}
}
}
}
{
"mcpServers": {
"shipvela": {
"url": "https://shipvela.com/mcp"
}
}
}