Shipbook

io.shipbookPublished by shipbook.ioOfficial publisherv1.1.0Updated Oct 24, 2026

Debug production issues using Shipbook logs and Loglytics error insights.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Shipbook's remote MCP server lets an AI assistant search application logs, review classified errors, and debug production issues using real runtime data.

What you can do
List apps in the account and create new apps with their credentials (name, appId, key). Retrieve grouped, classified errors with occurrence counts from the Loglytics engine. Search logs with 20+ filters such as severity, user, device and time. Investigate sessions and trace what happened to a specific user. Pre-built skills help install the SDK, audit logs for PII and wrong log levels, and group issues by root cause.
When to use it
Useful when debugging production or crash issues in a mobile or web app and you want the assistant to work from real logs and error classifications instead of guesses. Also fits teams that want help integrating the Shipbook SDK or auditing existing logging for sensitive data.
Requirements
A remote MCP endpoint at api.shipbook.io/mcp over streamable HTTP. A Shipbook account is required. Authentication uses OAuth 2.1 with a browser login and authorization on first use; clients without OAuth support can use an API key from the Shipbook console sent as an Authorization Bearer header.
Before you install
The server can create new apps and return their credentials, and it reads production logs that may contain user, device and session data, including personal information. Log auditing skills scan your codebase. Access is granted to your Shipbook account through OAuth or an API key, so treat that token as a secret and review what the assistant is allowed to read or create.

Installation

In SourceWeft

  1. Open Shipbook in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.shipbook%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "shipbook": {
      "type": "http",
      "url": "https://api.shipbook.io/mcp"
    }
  }
}

README

Shipbook MCP

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.

Supported Platforms

Works with any MCP-compatible AI assistant:

MCP Tools

ToolDescription
get-account-appsList all apps in your account (name, appId, platform, key, integration)
create-appCreate a new app and get its credentials (name, appId, key)
get-loglytics-errorsRetrieve grouped/classified errors with occurrence counts
get-logsSearch logs with 20+ filters (severity, user, device, time, etc.)

AI Skills

Pre-built investigation and integration workflows (available in Cursor and Claude Code):

SkillDescription
install-shipbookFull SDK integration assistant — installs package, detects wrappers, sets log levels, integrates Crashlytics, adds API logging, audits for PII
audit-logsScan codebase for PII in logs, incorrect log levels, and sensitive data leaks
list-issuesList and analyze classified errors/warnings from Loglytics, group by root cause
debug-sessionTrace a user's session to understand what happened
search-logsSearch logs using natural language queries

Installation

Cursor

From Cursor Marketplace: Search for "Shipbook" in the Cursor marketplace and click Install.

One-Click Install:

[Install Shipbook MCP in Cursor]

Manual Configuration: Open Cursor Settings → Tools & MCP → Add MCP server:

json
{  "mcpServers": {    "shipbook": {      "url": "https://api.shipbook.io/mcp",      "auth": {        "CLIENT_ID": "a1db8df5-ceb5-4013-8c35-af9e457c69b5"      }    }  }}

Claude Code

terminal
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.

Claude.ai

  1. Go to claude.ai → Settings → Connectors
  2. Click Add Connector and enter: https://api.shipbook.io/mcp
  3. Click Connect — you'll be redirected to Shipbook to authorize access

VS Code (Copilot)

One-Click Install:

[Install Shipbook MCP in VS Code]

Manual: Open Command Palette → MCP: Add Server → HTTP → https://api.shipbook.io/mcp

Codex

Add to ~/.codex/config.toml:

toml
[mcp_servers.shipbook]url = "https://api.shipbook.io/mcp"

Then: codex mcp login shipbook

Google Antigravity

Open MCP store → Manage MCP Servers → View raw config → Add:

json
{  "mcpServers": {    "shipbook": {      "url": "https://api.shipbook.io/mcp"    }  }}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "shipbook": {      "url": "https://api.shipbook.io/mcp"    }  }}

Generic MCP Client

MCP endpoint: https://api.shipbook.io/mcp

Standard mcpServers configuration:

json
{  "mcpServers": {    "shipbook": {      "url": "https://api.shipbook.io/mcp"    }  }}

Authentication

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:

json
{  "mcpServers": {    "shipbook": {      "url": "https://api.shipbook.io/mcp",      "headers": {        "Authorization": "Bearer YOUR_AUTH_TOKEN"      }    }  }}

Usage Examples

  • "Install Shipbook in my project"
  • "Audit my logs for PII and incorrect log levels"
  • "Find errors in my app and suggest fixes"
  • "What happened to the user with email [email protected]?"
  • "Show me logs from the last hour with severity Error"
  • "Investigate the most common crash in my iOS app"
  • "Debug the session where user X reported a problem"
  • "Fix the issues found in Shipbook Loglytics"

Documentation

License

MIT

Source: README.md at commit 788a220

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts