Debug production issues using Shipbook logs and Loglytics error insights.
Debug production issues using Shipbook logs and Loglytics error insights.
Is it safe?
No package registry to scan for CVEs.
No authentication — any process on your machine can connect to this server.
License not specified.
Last scanned 0 days ago.
Is it maintained?
Last commit 3 days ago.
Will it work with my client?
Transport: stdio, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
How much context will it use?
0 tools. Token cost not measured.
What if it doesn't work?
Common issues: JSON syntax errors in config, network or firewall blocking. Setup guide covers troubleshooting.
{
"mcpServers": {
"shipbook": {
"url": "https://api.shipbook.io/mcp",
"auth": {
"CLIENT_ID": "a1db8df5-ceb5-4013-8c35-af9e457c69b5"
}
}
}
}No automated test available for this server. Check the GitHub README for setup instructions.
Last scanned 4h ago
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.