Skip to main content
Glama
suryanshp1

Weather MCP Server

by suryanshp1
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

MCP Crash Course

A simple demo of MCP python sdk.

uv commands

start a new project

uv init <project-name>

create a virtual environment

uv venv

activate the virtual environment

uv venv --activate

install the dependencies

uv add <package>
uv add -r requirements.txt
uv sync

run application

uv run app.py

run the development server

uv run dev

build the project

uv run build

Run server using MCP Inspector :

  • Install MCP python sdk

uv add "mcp[cli]"

  • Run mcp inspector

uv run mcp dev server/weather.py

MCP Inspector is up and running at http://127.0.0.1:6274

Add server to claude desktop :

  • run command

uv run mcp install .\server\weather.py

  • query "what is weather alert in CA" in claude desktop

Add server to cursor :

  • goto preferences > settings > mcp and copy paste claude config

{
  "mcpServers": {
    "weather": {
      "command": "uv",
      "args": [
        "run",
        "--with",
        "mcp[cli]",
        "mcp",
        "run",
        "C:\\Users\\Suraj\\Desktop\\Python\\mcp-crash-course\\mcpcrashcourse\\server\\weather.py"
      ]
    }
  }
}

  • Then do a query in cursor chat

Directly consume server in code - using mcp-use :

  • Install mcp-use

uv add mcp-use

  • Install langchain-groq

uv add langchain-groq

  • run client

uv run server/client.py

Available Tools

1 tool
get_alertsC

Get weather alerts for US state Args: state: Two letter US state code (e.g CA, NY etc)

ParametersJSON Schema
NameRequiredDescriptionDefault
stateYes

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool 'Get weather alerts' but does not describe behavioral traits such as rate limits, authentication needs, error handling, or what the return format looks like. For a tool with no annotations, this is a significant gap in transparency.

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

Conciseness3/5

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

The description is appropriately sized with two sentences, but it is not optimally structured. The first sentence states the purpose, and the second explains the parameter, but it could be more front-loaded with key details. It avoids waste but lacks polish in organization.

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

Completeness2/5

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

Given the complexity (simple tool with one parameter), no annotations, and no output schema, the description is incomplete. It covers the purpose and parameter semantics but misses behavioral context, usage guidelines, and output details. For a tool with no structured support, more comprehensive description is needed.

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

Parameters4/5

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

The schema description coverage is 0%, so the description must compensate. It adds meaning by specifying that the 'state' parameter is a 'Two letter US state code (e.g CA, NY etc)', which clarifies the format and provides examples. This is valuable beyond the basic schema, though it could be more detailed (e.g., list of valid codes).

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Get weather alerts for US state' specifies the verb ('Get'), resource ('weather alerts'), and geographic scope ('US state'). It distinguishes the tool's function well, though without sibling tools, full differentiation isn't tested. The purpose is specific and actionable.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or context for invocation. It only states what the tool does without indicating scenarios, limitations, or comparisons to other tools. This leaves the agent without usage direction.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently follows a consistent naming pattern. The tool name 'get_alerts' uses a clear verb_noun format, which would be consistent if more tools were added.

Tool Count2/5

A single tool is too few for a weather server, as it lacks basic operations like getting current conditions, forecasts, or historical data. This severely limits the server's utility and scope.

Completeness1/5

The tool set is severely incomplete for a weather domain. It only provides alerts for US states, missing essential functions such as retrieving current weather, forecasts, or data for locations outside the US, making it inadequate for typical weather-related tasks.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP Server Basic Example

    dorisashehi
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    A basic Model Context Protocol server implementation that demonstrates core MCP functionality including tools and resources. Provides weather alerts through the Weather API and serves as a learning example for MCP development.

  • Weather MCP Server

    264Gaurav
    F
    license
    A
    quality
    D
    maintenance
    Demonstrates creating and connecting an MCP weather server using FastMCP, with support for integration with Claude Desktop, Cursor, and local LLMs to query weather alerts and information.
    1
    1

  • MCP Quickstart Weather Server

    veysby
    F
    license
    B
    quality
    D
    maintenance
    A basic MCP server adapted from the official quickstart guide that provides weather data functionality and works with OpenAI chat completions API. Demonstrates MCP server setup with configuration examples for Claude Desktop and development tools.
    2

  • mcp-weather

    minwoo129
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server built with the mcp-framework to provide weather-related tools and data to AI clients. It enables integration of weather capabilities and custom tools into the MCP ecosystem for use with platforms like Claude Desktop.
    23

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/suryanshp1/mcpcrashcourse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server