Weather
Wire a minimal weather MCP server into Claude Code or Cursor while learning stdio MCP on Windows.
Overview
io.github.StarHawkMK1/weather is an MCP server for the Build phase that exposes weather tools over stdio for Windows MCP tutorials and agent integration practice.
What is this MCP server?
- Published on npm as @starhawk/mcp-weather-server (v1.0.2) with stdio transport
- Official MCP server.schema.json manifest for registry-compatible registration
- Small reference surface ideal for copying patterns before production APIs
- GitHub source at StarHawkMK1/mcp-weather-server for local forks and edits
- Windows-focused tutorial path for first-time MCP authors
- Server version 1.0.2 on npm as @starhawk/mcp-weather-server
- Transport: stdio only in published manifest
- 1 npm package entry in server.schema.json
What problem does it solve?
You want to prove MCP wiring on Windows without building a custom server from scratch.
Who is it for?
First MCP server on Windows, stdio transport experiments, and copy-paste templates before production weather APIs.
Skip if: Accurate forecasting, SLA-backed ops weather, or teams that already run mature HTTP MCP gateways.
What do I get? / Deliverables
Your agent can call a registered weather MCP tool locally so you can move on to real APIs and deployment patterns.
- Working stdio MCP weather tools callable from your agent
- Reusable server.json manifest pattern for other MCP projects
- Confidence to swap the tutorial backend for a paid forecast API
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the repo is framed as a hands-on Windows tutorial for implementing and registering an MCP server, not for market research or launch work. Integrations is the right subphase: the server exposes weather data to agents over MCP stdio, matching third-party API bridge patterns solo builders copy into their stack.
How it compares
Tutorial stdio MCP integration, not a hosted product-idea or commerce server.
Common Questions / FAQ
Who is io.github.StarHawkMK1/weather for?
Indie builders and students who need a minimal, npm-installable MCP weather example on Windows before touching production integrations.
When should I use io.github.StarHawkMK1/weather?
Use it during Build when you are registering your first stdio MCP server and want live tool calls without authoring transport boilerplate.
How do I add io.github.StarHawkMK1/weather to my agent?
Install @starhawk/mcp-weather-server from npm, add a stdio MCP entry in Claude Code or Cursor pointing at that package, restart the client, and confirm the weather tools appear in the MCP panel.