
Weather
Give your coding agent live weather lookups through MCP while you prototype apps, automations, or location-aware features.
Overview
Byrness Weather is a MCP server for the Build phase that supplies weather information tools to coding agents over stdio npm transport.
What is this MCP server?
- stdio npm package @byrness/mcp-weather-server for local agent registration
- Single-purpose weather information tools for agent-driven queries
- Registry version 1.0.8 with GitHub source mcp-weather-server
- Lightweight dependency surface for indie side projects
- Publisher metadata references documentation endpoint for setup details
- Registry package version 1.0.8 (stdio)
- npm identifier @byrness/mcp-weather-server
- stdio transport type in server.schema.json
What problem does it solve?
You want weather data inside agent workflows without writing and maintaining a one-off API wrapper for every prototype.
Who is it for?
Beginners prototyping location or weather-dependent features who want the smallest possible MCP weather bridge.
Skip if: Production operations teams that need historical climate analytics, SLA-backed feeds, or ship-phase observability dashboards.
What do I get? / Deliverables
After install, your agent can fetch weather information through MCP while you build integrations or test tool-calling UX.
- Agent-invokable weather information MCP tools
- Local stdio MCP server wired into your dev environment
- Faster weather-feature prototyping without custom HTTP glue
Recommended MCP Servers
Journey fit
Build is the right shelf because weather is a backend/integration concern you wire into product demos or agent tools, not a growth or ops monitoring platform. integrations matches small, focused MCP data providers that agents call from application code paths.
How it compares
Thin weather data MCP integration, not a monitoring or infra cost server.
Common Questions / FAQ
Who is byrness weather for?
Indie developers and agent users who need simple weather lookups from Claude Code, Cursor, or other stdio MCP hosts while building apps or automations.
When should I use byrness weather?
Use it during Build integrations when your prototype or agent demo needs live weather without a custom API client.
How do I add byrness weather to my agent?
Add @byrness/mcp-weather-server to your MCP config with stdio transport per the package registry entry and follow the publisher documentation URL in server metadata.