Clean TypeScript starter for MCP servers: zod-validated tools, tests, one-command dev loop.
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.
npx degit colossal1598/ship-MCP my-server && cd my-server && npm i && npm run dev
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.
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.npm install
npm run dev # run the server (stdio)
npm test # unit tests
npm run inspect # poke tools in the MCP Inspector UI
npm run build # compile to dist/
{
"mcpServers": {
"my-server": {
"command": "node",
"args": ["/absolute/path/to/dist/index.js"]
}
}
}
// src/tools.ts
export const greetInput = { name: z.string() };
export async function greet({ name }: { name: string }) {
return { content: [{ type: "text" as const, text: `Hello, ${name}!` }] };
}
// src/index.ts
server.registerTool("greet", { description: "Greet someone", inputSchema: greetInput }, greet);
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:
One-time $49, MIT-licensed output, free updates. → Get Ship MCP Pro
MIT © Argo Navis
Note on the SDK pin: this starter pins
@modelcontextprotocol/server@2.0.0-beta.5exactly — the v2 SDK for the 2026-07-28 spec. When the stable2.0.0lands, 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-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y ship-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-colossal1598-ship-mcp": {
"command": "npx",
"args": [
"-y",
"ship-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceio.github.colossal1598/ship-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.