MCP Weather Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Weather ServerWhat's the current weather in Paris?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
π€οΈ MCP Weather Server
A lightweight and fast Model Context Protocol (MCP) server built in Python that equips AI assistants (like Claude Desktop) with real-time weather information using wttr.in.
β¨ Features
β‘ Real-time Weather: Fetch instant temperature and weather updates for any location worldwide.
π Standard MCP Compliance: Built with the official Python
mcpSDK using standardstdiotransport.π Blazing Fast Setup: Managed with
uvfor near-instant dependency management.π€ Seamless Claude Integration: Easily connectable with Claude Desktop or any MCP-compatible AI client.
Related MCP server: Weather MCP
π οΈ Tools Exposed
Tool Name | Parameters | Description | Example Output |
|
| Retrieves current temperature for the specified city/location |
|
π Prerequisites
Python: Version
3.12or neweruv: Fast Python package installer and resolver (Installation Guide)
Claude Desktop (Optional, for Claude Desktop integration)
π Quick Start
1. Clone the Repository
git clone https://github.com/g-adarshg098/MCP_SERVER.git
cd MCP_SERVER2. Install Dependencies
Using uv:
uv syncOr using standard pip:
python -m venv .venv
# On Windows:
.venv\Scripts\activate
# On macOS/Linux:
source .venv/bin/activate
pip install -e .3. Test Running the Server
Run directly with uv:
uv run mcp-weather.pyπ₯οΈ Claude Desktop Integration
To use this weather tool inside Claude Desktop, add the server configuration to your claude_desktop_config.json.
Config File Location
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Configuration
Add the following to your mcpServers object:
Windows (with uv)
{
"mcpServers": {
"weather": {
"command": "uv",
"args": [
"--directory",
"C:\\Users\\adars\\OneDrive\\ADARSHG\\GENAI_2\\MCP_Server",
"run",
"mcp-weather.py"
]
}
}
}Note: Make sure to update the absolute path to match your project's directory location on your machine.
macOS / Linux (with uv)
{
"mcpServers": {
"weather": {
"command": "uv",
"args": [
"--directory",
"/path/to/MCP_Server",
"run",
"mcp-weather.py"
]
}
}
}After modifying the configuration, restart Claude Desktop. You should see the π¨ hammer icon indicating available tools, including get_weather!
π Project Structure
MCP_SERVER/
βββ src/
β βββ mcp_server/
β βββ __init__.py
βββ mcp-weather.py # Weather MCP server implementation
βββ pyproject.toml # Project metadata and dependencies
βββ uv.lock # Lockfile for reproducible builds
βββ .env.example # Template for environment variables
βββ .gitignore # Git ignore rules
βββ README.md # Project documentationπ€ Contributing
Contributions, issues, and feature requests are welcome! Feel free to check the issues page.
π€ Author
Adarsh G
GitHub: @g-adarshg098
Email: its.adarshg15@gmail.com
π License
This project is licensed under the MIT License.
Available Tools
1 toolget_weatherD
| Name | Required | Description | Default |
|---|---|---|---|
| location | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
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. Dates show when Glama detected each change.
1 tool update
v0.1.0- First observed
get_weather
TDQS
With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clear from its name: get_weather.
The only tool follows a clear verb_noun pattern (get_weather), which is consistent and predictable. There are no other tools to introduce naming conflicts.
A weather-focused server with only one tool feels too sparse. Typical weather servers offer current conditions, forecasts, and alerts, so the single get_weather tool is underdeveloped for the apparent scope.
The one tool provides only a generic weather lookup, missing likely needed operations such as forecasts, historical weather, or alerts. This represents a significant gap for a weather server's expected capabilities.
Maintenance
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
Get current weather for any city and create images from your prompts. Streamline planning, reportsβ¦
Provide real-time and forecast weather information for locations in the United States using naturaβ¦
Current weather and forecasts for any coordinates, backed bβ¦ β paid per call (x402/credits), 1 tools
Real-time data API for AI Agents: stocks, weather, forex, logistics, search, scrape, news, IP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides real-time weather information and forecasts, connecting AI assistants with live weather data for current conditions and multi-day forecasts for any location worldwide.-
- AlicenseNot gradedqualityDmaintenanceEnables users to get real-time weather information for any city in the world. Provides current temperature and weather conditions through a simple city name query.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to fetch current weather conditions and forecasts for any city using the Open-Meteo API. Provides temperature, precipitation, and hourly forecast data through natural language queries.-
- FlicenseBqualityDmaintenanceEnables users to retrieve current weather information for any city location. Provides a simple interface to fetch weather data through natural language queries.1-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/g-adarshg098/MCP_SERVER'
If you have feedback or need assistance with the MCP directory API, please join our Discord server