Ship Mcp

io.github.colossal1598Published by GitHub account colossal1598v0.2.1Updated Oct 24, 2026

Clean TypeScript starter for MCP servers: zod-validated tools, tests, one-command dev loop.

The publisher's own server: ship.page

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

A TypeScript starter template for building your own MCP servers, with zod-validated example tools, tests, and a dev loop.

What you can do
Ships a minimal MCP server scaffold: server wiring with stdio transport in src/index.ts, tool logic kept separate in src/tools.ts, and Vitest unit tests that run without spawning the server. Two example tools are included, echo and fetch_json, the latter showing async work with error handling. Scripts cover running the dev server, testing, building to dist, and opening the official MCP Inspector against the dev server.
When to use it
Use it when you want to author a new MCP server in TypeScript and would rather start from working SDK wiring, schema validation, stderr logging, and Inspector setup than repeat that setup yourself. It is a development scaffold, not a ready-made server with useful end-user tools.
Requirements
Node.js and npm on the local machine; the package is installed from npm and run as a local stdio process. The README's quickstart uses npx degit to copy the repository, then npm install, npm run dev, npm test, npm run inspect, and npm run build. No accounts, API keys, or environment variables are declared.
Before you install
The starter pins an exact beta version of the MCP SDK, so upstream beta changes will not be picked up until you bump the pin and re-run tests. The README also promotes a separate paid product, Ship MCP Pro, with license-key gating, usage metering, and HTTP transport; that is a different offering and not part of this package. The example fetch_json tool performs outbound network requests when used.

Installation

In SourceWeft

  1. Open Ship Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ship-mcp

The clean TypeScript starter for building MCP servers. Zod-validated tools, unit tests, MCP Inspector wired up, one-command dev loop. Clone it, rename two strings, ship your server.

bash
npx degit colossal1598/ship-MCP my-server && cd my-server && npm i && npm run dev

Why this exists

Every MCP server starts with the same 90 minutes of setup: SDK wiring, stdio transport, schema validation, figuring out why console.log breaks the protocol (logs go to stderr — already handled here), and getting the Inspector attached. This repo is that 90 minutes, done properly, once.

What's inside

  • src/index.ts — server wiring: register tools, connect stdio transport. ~40 lines, no magic.
  • src/tools.ts — tool logic decoupled from wiring so it's unit-testable. Two examples: echo (hello-world) and fetch_json (real async tool with error handling).
  • src/tools.test.ts — Vitest tests that run without spawning the server.
  • npm run inspect — opens the official MCP Inspector against your dev server.

Quickstart

bash
npm installnpm run dev        # run the server (stdio)npm test           # unit testsnpm run inspect    # poke tools in the MCP Inspector UInpm run build      # compile to dist/

Use it from Claude Desktop / Claude Code

json
{  "mcpServers": {    "my-server": {      "command": "node",      "args": ["/absolute/path/to/dist/index.js"]    }  }}

Add your own tool (30 seconds)

ts
// src/tools.tsexport const greetInput = { name: z.string() };export async function greet({ name }: { name: string }) {  return { content: [{ type: "text" as const, text: `Hello, ${name}!` }] };}
// src/index.tsserver.registerTool("greet", { description: "Greet someone", inputSchema: greetInput }, greet);

Want to ship a paid MCP server?

Fewer than 5% of the 11,000+ MCP servers out there make money — not because the demand isn't there, but because the billing plumbing is genuinely annoying. Ship MCP Pro is this starter plus everything the free version deliberately leaves out:

  • 🔑 License-key gating — Payhip & Gumroad license verification middleware; sell keys, server validates them
  • 📊 Usage metering + per-key rate limits — free tier / paid tier out of the box
  • 🌐 Streamable HTTP transport — deploy as a remote server (Docker + Railway/Fly guides included)
  • ✅ CI pipeline, expanded test suite, production error handling
  • 📣 Launch kit — the exact directory-submission checklist + listing templates that get servers 10x more installs

One-time $49, MIT-licensed output, free updates. → Get Ship MCP Pro


MIT © Argo Navis

Note on the SDK pin: this starter pins @modelcontextprotocol/[email protected] exactly — the v2 SDK for the 2026-07-28 spec. When the stable 2.0.0 lands, bump the pin and re-run the tests; the exact pin is there so an upstream beta change can't silently break your build.

Source: README.md at commit 165d3a2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

Other Ship integrations