Shipstar

ai.shipstarPublished by shipstar.aiOfficial publisherv1.6.0Updated Nov 6, 2026

Generate changelogs, release emails, help-center articles, banners, and social posts from commits.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Shipstar turns commits into release content — changelogs, release emails, help-center articles, banners and social posts — for an assistant to generate.

What you can do
  • Generate release content from commits: changelogs, release emails, help-center articles, banners and social posts.
  • The registry lists no individual tools, so the exact operations are not documented here.
  • It is a hosted remote service reached over streamable HTTP rather than a local package.
When to use it
Useful when a team ships software regularly and wants release notes and launch messaging drafted from commit history instead of written by hand.
Requirements
A remote MCP endpoint at mcp.shipstar.ai over streamable HTTP. OAuth authentication is required, so the user must sign in to a Shipstar account; no environment variables or headers are declared.
Before you install
OAuth grants the server access to the user's Shipstar account, and commit data is sent to a third-party hosted service. Generated content may be published or sent to customers, so review it before use.

Installation

In SourceWeft

  1. Open Shipstar 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/ai.shipstar%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": {
    "shipstar": {
      "type": "http",
      "url": "https://mcp.shipstar.ai/mcp"
    }
  }
}

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

3
  1. v1.6.0LatestNov 6, 2026
  2. v1.5.0Sep 29, 2026
  3. v1.4.1Sep 16, 2026

Score

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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.