Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Debug production issues using Shipbook logs and Loglytics error insights.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.shipbook.io/mcp在终端中运行这条命令
claude mcp add --transport http shipbook https://api.shipbook.io/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"shipbook": {
"url": "https://api.shipbook.io/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"shipbook": {
"type": "http",
"url": "https://api.shipbook.io/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.shipbook.io/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 shipbook.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.1.0)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, FlyDocs
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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