Skip to main content
Glama
ai-makes-sense

Weather and Tasks MCP Server

by ai-makes-sense
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

What is MCP? — sample code

Two real, runnable MCP servers for the video — one that reads the world and one that writes to it — plus a boilerplate template to build your own. No API keys. Runs on Windows, macOS, and Linux.

▶️ Video: (link at publish) · 📬 Newsletter: (link)

What's here

File

Does

Shows

weather_server.py

live weather for any city (Open-Meteo, keyless)

a read tool — your AI reaching the real world

tasks_server.py

a to-do list it can add to / complete / list

write tools — your AI taking action and changing state

server_template.py

boilerplate to copy

how to build your own

client.py

tests both servers without Claude

Related MCP server: MCP Weather Server

1. Test it in 2 minutes (no Claude needed)

Install uv (one line, any OS), then from this folder:

uv run python client.py

You'll see a read demo and a write demo:

weather_server.py  tools: ['get_weather']
  get_weather({'city': 'Tokyo'}) -> Tokyo, Japan: 21.7°C, mainly clear, wind 4.4 km/h.

tasks_server.py  tools: ['add_task', 'complete_task', 'list_tasks']
  add_task({'task': 'record episode 2'}) -> Added: 'record episode 2'  (you now have 1 task(s)).
  complete_task({'number': 1}) -> Completed: 'record episode 2'.
  list_tasks({}) -> 1. [x] record episode 2

The tasks server writes to a tasks.json right next to it — open the file and you'll see exactly what your AI changed.

2. Connect them to Claude

  • macOS — ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows — %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "weather": { "command": "uv", "args": ["--directory", "ABSOLUTE/PATH/TO/THIS/FOLDER", "run", "python", "weather_server.py"] },
    "tasks":   { "command": "uv", "args": ["--directory", "ABSOLUTE/PATH/TO/THIS/FOLDER", "run", "python", "tasks_server.py"] }
  }
}

Restart Claude, then try:

  • Read: "What's the weather in Tokyo right now?"

  • Write: "Add 'finish the thumbnail' to my tasks." → then "What's on my list?"

3. Build your own

Open server_template.py, rename the server, and replace do_something with your tool — read a file, hit an API, write to a database. Uncomment the resource/prompt examples for those too, then point Claude at it the same way.

Read vs. write — and the one safety note

weather_server only reads. tasks_server writes (it changes tasks.json). That write power — letting your AI actually do things — is the whole point of MCP. It's also exactly why you only connect servers you trust, and why real tools add confirmations and permissions before destructive actions.

Why it's cross-platform

Pure Python + the standard library for HTTP (urllib), local files via pathlib, and sys.executable to launch servers — no OS-specific paths or shells. Only dependency: the mcp SDK.

MIT licensed. Built for the AI Makes Sense channel.

Available Tools

1 tool
get_weatherA

Get the current weather for a city anywhere in the world.

Example: get_weather("Tokyo") -> "Tokyo, Japan: 18.4°C, partly cloudy, wind 9 km/h".

ParametersJSON Schema
NameRequiredDescriptionDefault
cityYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses a read operation but provides no additional behavioral context (e.g., data freshness, error handling). Without annotations, it is adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with a clear statement and example. No wasted words, front-loaded purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, has output schema, no siblings), the description provides sufficient context with purpose, example, and output format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description only adds an example of the city parameter format. It does not elaborate on constraints, defaults, or expected input variations beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves current weather for any city worldwide, with a specific verb and resource. No siblings exist, so differentiation is unnecessary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through an example but lacks explicit when-to-use or when-not-to-use guidance. No alternatives exist, so minimal guidelines are acceptable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedget_weather
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools.

Naming Consistency5/5

With a single tool, naming is trivially consistent; the verb_noun pattern is followed.

Tool Count2/5

A single tool is insufficient for a server named 'Weather and Tasks', which implies at least a weather and a task tool.

Completeness2/5

The server only provides a basic weather retrieval function, lacking forecast or task capabilities, making it incomplete for its stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP_3

    sunhuiowo
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides paper search and management capabilities along with weather queries, demonstrating MCP integration for AI systems to interact with external resources and tools.
    -

  • MCP Weather Server

    deepcodes7
    F
    license
    B
    quality
    D
    maintenance
    Enables AI agents to retrieve real-time weather conditions and forecasts via OpenWeatherMap API. Supports interactive weather queries and travel planning through MCP tools, resources, and prompts.
    2
    -

  • Atlas MCP Server

    good2idnan
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents and users to manage workspace files, monitor system metrics, take persistent notes, and retrieve weather data via MCP tools and resources.
    -