ShipLog

io.github.amacgregorPublished by GitHub account amacgregorv1.0.0Updated Oct 30, 2026

Read user feedback and draft your changelog from any MCP client.

The publisher's own server: ship.page

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

ShipLog's hosted MCP server lets an assistant read a ShipLog feedback board, add and triage feedback, and draft or publish changelog entries.

What you can do
  • List and search feedback items, sorted by votes or date, or by keyword across titles and descriptions
  • Summarize the board: total count, counts by status and top-voted items
  • Add new feedback items and move existing ones between statuses such as planned, in progress or completed
  • List changelog entries newest first, including drafts, and write new entries saved as drafts unless published
When to use it
Useful for solo SaaS founders or small teams already running a ShipLog board who want to review user feedback, triage requests and turn shipped work into changelog entries without leaving their editor or chat client.
Requirements
A remote Streamable HTTP endpoint hosted by ShipLog; nothing to install. Requires a ShipLog project API key from Settings > API keys, sent as an Authorization bearer header. Each key is scoped to one project. Available on every plan, including free.
Before you install
The Authorization header carries a live project API key, so keep it out of shared configs and logs. The server can create feedback items, change their status and publish changelog entries, which changes data visible on your public board. There are no delete, billing or key management tools.

Installation

In SourceWeft

  1. Open ShipLog in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.github.amacgregor%2Fshiplog/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.

{
  "mcpServers": {
    "shiplog": {
      "type": "http",
      "url": "https://shiplog.ca/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

ShipLog MCP server

ShipLog is a feedback board, public changelog and roadmap with an embeddable widget, made for solo SaaS founders.

Its remote MCP server lets Claude Code, Claude Desktop, Cursor or any MCP client work with your board from the editor. Ask for a summary of top-voted feedback, search what users asked for, add feedback items, mark an item shipped, and write the changelog entry as a draft or publish it.

This repo holds the listing metadata only. The server is hosted by ShipLog, so there's nothing to install or run.

Connect

  • Endpoint: https://shiplog.ca/mcp
  • Transport: Streamable HTTP
  • Auth: a project API key from ShipLog under Settings > API keys, sent as Authorization: Bearer sl_live_.... Each key is scoped to one project.
  • Plans: available on every plan, including free.

Claude Code:

bash
export SHIPLOG_API_KEY=sl_live_YOUR_KEYclaude mcp add --transport http shiplog https://shiplog.ca/mcp --header "Authorization: Bearer ${SHIPLOG_API_KEY}"

Cursor, Claude Desktop and other JSON-configured clients:

json
{  "mcpServers": {    "shiplog": {      "type": "http",      "url": "https://shiplog.ca/mcp",      "headers": { "Authorization": "Bearer ${SHIPLOG_API_KEY}" }    }  }}

Tools

ToolWhat it does
list_feedbackList feedback items sorted by votes or date
search_feedbackKeyword search across feedback titles and descriptions
feedback_summaryTotal count, counts by status and the top-voted items
create_feedbackAdd a feedback item to the board
update_feedback_statusMove an item to planned, in progress, completed and so on
list_changelogList changelog entries, newest first, including drafts
create_changelog_entryWrite a changelog entry, saved as a draft unless you publish it

There are no delete, billing or key management tools.

Links

Source: README.md at commit 64739aa

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

75% 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

    Declare a license in the repository or the registry entry.

Other Ship integrations