Install it and your client gains nothing on its own — the value is the layout and the `create-tool` script, which keep schema, implementation and test together as you add tools. Judge it against your own boilerplate, not against servers that do something.
A starter template rather than a server that does a job. It lays out a Bun + TypeScript project — `src/tools/` for tool implementations, `src/utils/` for shared code, `main.ts` as the entry point — and ships a script that creates a new tool directory for you.
- A one-command tool generator: `bun run scripts/create-tool.ts <tool-name>` writes the implementation file, the JSON schema for its parameters, and a test file, then registers it in the tools index
- Bun wired up for tests and development, and Biome for linting and formatting
- Version bumps handled by standard-version, driven by `feat` / `fix` / `BREAKING CHANGE` commit messages
- A build step whose output you point Claude Desktop at as `dist/main.js`
Bun, for install, test, lint and build. Nothing else: no account, no key, no external service. The npm package name is `mcp-starter`. A Smithery install exists if you want to run the template as-is against Claude Desktop.
One command — npx -y @smithery/cli install @GreatAuk/mcp-weather --client claude