Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Debug production issues using Shipbook logs and Loglytics error insights.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.shipbook.io/mcpRun this in your terminal
claude mcp add --transport http shipbook https://api.shipbook.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"shipbook": {
"url": "https://api.shipbook.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"shipbook": {
"type": "http",
"url": "https://api.shipbook.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.shipbook.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain shipbook.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Tools MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Connect Shipbook to any AI coding assistant to investigate issues using real application logs. Shipbook's Loglytics engine automatically classifies errors and provides structured insights, while powerful log search lets AI agents explore runtime events. Logs include rich context — severity, user, device, session, and the exact file and code location — giving your assistant the ground truth it needs to debug effectively.
Prerequisites: A Shipbook account. Get started here.
Works with any MCP-compatible AI assistant:
| Tool | Description |
|---|---|
| get-account-apps | List all apps in your account (name, appId, platform, key, integration) |
| create-app | Create a new app and get its credentials (name, appId, key) |
| get-loglytics-errors | Retrieve grouped/classified errors with occurrence counts |
| get-logs | Search logs with 20+ filters (severity, user, device, time, etc.) |
| get-alerts | List the alerts that fired for an app, most recent first: custom log-filter alerts and automatic Loglytics alerts |
| get-alert | Get one fired alert by its ID, e.g. the id from a Shipbook webhook payload |
| get-daily-stats | Daily stats per version (sessions, users, devices, logs by severity) with crash-free, error-free and warning-free rates |
| get-releases | Release health, newest first: adoption, crash-free sessions, and new and regressed issues per version, with deploy markers |
Pre-built investigation and integration workflows (available in Cursor and Claude Code):
| Skill | Description |
|---|---|
| install-shipbook | Full SDK integration assistant — installs package, detects wrappers, sets log levels, integrates Crashlytics, adds API logging, audits for PII |
| audit-logs | Scan codebase for PII in logs, incorrect log levels, and sensitive data leaks |
| list-issues | List and analyze classified errors/warnings from Loglytics, group by root cause |
| debug-session | Trace a user's session to understand what happened |
| search-logs | Search logs using natural language queries |
From Cursor Marketplace: Search for "Shipbook" in the Cursor marketplace and click Install.
One-Click Install:
Manual Configuration: Open Cursor Settings → Tools & MCP → Add MCP server:
{
"mcpServers": { "shipbook": { "url": "https://api.shipbook.io/mcp", "auth": { "CLIENT_ID": "a1db8df5-ceb5-4013-8c35-af9e457c69b5" } } } }
claude mcp add --transport http shipbook-mcp https://api.shipbook.io/mcp
On first use, Claude Code opens your browser to log in and authorize access.
https://api.shipbook.io/mcpOne-Click Install:
Manual: Open Command Palette → MCP: Add Server → HTTP → https://api.shipbook.io/mcp
Add to ~/.codex/config.toml:
[mcp_servers.shipbook]
url = "https://api.shipbook.io/mcp"
Then: codex mcp login shipbook
Open MCP store → Manage MCP Servers → View raw config → Add:
{
"mcpServers": { "shipbook": { "url": "https://api.shipbook.io/mcp" } } }
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": { "shipbook": { "url": "https://api.shipbook.io/mcp" } } }
MCP endpoint: https://api.shipbook.io/mcp
Standard mcpServers configuration:
{
"mcpServers": { "shipbook": { "url": "https://api.shipbook.io/mcp" } } }
Shipbook MCP uses OAuth 2.1 for secure authentication. On first use, you'll be redirected to Shipbook to log in and authorize access. Your credentials are never shared with the AI assistant.
For MCP clients that don't support OAuth, you can use an API key from the Authentication Keys section in the Shipbook console:
{
"mcpServers": { "shipbook": { "url": "https://api.shipbook.io/mcp", "headers": { "Authorization": "Bearer YOUR_AUTH_TOKEN" } } } }
MIT