Skip to main content

​
Weather MCP Server Starter

​
Summary

This starter sketches a protocol-facing tool service that exposes a small, stable weather interface for agent use.

​
Status

starter

​
Why It Exists

Protocol examples are easier to reason about when they focus on one tool boundary. This starter keeps the scope to request validation, predictable tool shapes, and response packaging.

​
Folder Structure

weather-mcp-server-starter/
├── index.mdx
├── SOURCE_NOTES.mdx
└── src/
    ├── access_policy.py
    ├── server.py
    └── tool_manifest.py

​
Quick Start

This is a starter, not a finished server. The example file shows the interface shape and handler boundary without bringing in a full protocol runtime. For a repo-level smoke check, run python3 scripts/verify_example_projects.py from the repository root.

​
Included Sample Files

  • src/server.py: the minimal request and response boundary for one tool
  • src/tool_manifest.py: a compact example of how a protocol-facing starter can declare its input schema and output shape
  • src/access_policy.py: a small authorization boundary that keeps permission checks separate from the tool handler itself

​
Constraints

  • No transport layer is implemented.
  • No real weather API integration is included.
  • Authentication and permission rules are still placeholders.

​
Next Steps

  • Add a concrete transport surface.
  • Add permission checks and request logging.