some_function
The starter template's example tool: returns a greeting with the name and address you pass.
LABSCO SUMMARY
A project skeleton to copy, with one small weather tool as the worked example.
Installed as it is, your client gets get_alert — US weather alerts by state — and the template's example tool, nothing more. The value is the layout and the create-tool script, which keep schema, implementation and test together as you add tools; get_alert shows what one finished tool looks like. Judge it against your own boilerplate, not against full weather servers.
What it is
A starter template with one working tool in it: get_alert, which returns the National Weather Service alerts for a US state. 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.
What you get
- 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 CHANGEcommit messages - Two tools already registered: get_alert, which takes a two-letter state code and returns each alert's event, area, severity, status and headline, and some_function, the template's example
Requirements
Bun, for install, test, lint and build, and Node to run the built dist/main.js. No account and no key: get_alert reads the public api.weather.gov alerts feed.
Setup effort
Follow the published steps — bun install
USE CASES
01
Starting a new MCP server without picking a project layout first
Clone it, run the tool generator once per capability you want, and you have implementation, parameter schema and test stubs already wired into the index.
02
Keeping releases tidy on a server you publish to npm
Write commits as feat or fix, run the release script to bump the version and update the changelog, then publish. The convention is already configured.
2 tools
Listed in project code.
get_alert
Get weather alerts for a specific US state: each National Weather Service alert (current and recently expired) with its event, area, severity, status and headline.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools registered in the project's code. some_function is the starter template's example tool. get_alert is the working one: it reads the National Weather Service's public alerts feed for a two-letter US state code.
Requires
- Bun (bun install, bun run build)
- node on PATH
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/GreatAuk/mcp-weather
cd mcp-weather
bun install
bun run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp-weather": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PROJECT>/dist/main.js"
]
}
}
}<YOUR_PATH_TO_PROJECT> is the absolute path of your clone. dist/main.js exists after bun run build.
