Skip to main content
Glama
264Gaurav

Weather MCP Server

by 264Gaurav
README.md
# MCP Server Creation and MCP client connection (Agent-Claude,cursor or, custom server calling and integration with local LLMs).

This project demonstrates how to create and connect an MCP (Model Context Protocol) weather server using FastMCP.

> šŸ“– **Want to learn more about MCP?** Check out our [Comprehensive MCP Guide](Readme_MCP.md) for detailed explanations, concepts, and best practices.

## Prerequisites

- Python 3.13+
- `uv` package manager installed

## Setup Instructions

### 1. Initialize the Project

Initialize a new project using `uv`:

```bash
uv init
```

### 2. Create Virtual Environment

Create a virtual environment for the project:

```bash
uv venv
```

### 3. Activate Virtual Environment

Activate the virtual environment:

**Windows:**
```bash
.venv\Scripts\activate
```

**Linux/Mac:**
```bash
source .venv/bin/activate
```

### 4. Install MCP CLI

Add the MCP CLI package to enable fast MCP CLI commands:

```bash
uv add "mcp[cli]"
```

## Running the MCP Server

### Development Mode

To run the MCP server in development mode:

```bash
uv run mcp dev server/weather.py
```

**Expected Output:**
```
Starting MCP inspector...

āš™ļø Proxy server listening on localhost:6277
```

## Connecting to Claude Desktop

### Install Server to Claude

Add the weather server to Claude Desktop:

```bash
uv run mcp install server/weather.py
```

**Expected Output:**
```
Added server 'weather' to Claude config 

Successfully installed weather in Claude app
```

Once installed, you can ask Claude questions like:
- "What are the weather alerts in CA?"
- The MCP server will be called automatically and display the results.

### Manual Configuration for Cursor or Other Clients

For Cursor or other clients, you'll need to manually configure the server using the Claude Desktop config file format.

**Get the server configuration from:** `claude_desktop_config` file

**Example Configuration:**
```json
"weather": {
  "command": "C:\\Users\\gaura\\AppData\\Local\\Programs\\Python\\Python313\\Scripts\\uv.EXE",
  "args": [
    "run",
    "--with",
    "mcp[cli]",
    "mcp",
    "run",
    "C:\\Users\\gaura\\OneDrive\\Desktop\\AI projects\\mcp_project\\server\\weather.py"
  ]
}
```

**Note:** Update the paths in the configuration to match your system paths.

**Usage in Cursor:**
- Go to **MCP** → **mcp config.json**
- Add the configuration above

## Using MCP with Local LLMs (mcp-use)

`mcp-use` allows you to connect to MCP servers directly without an AI agent for programmatic tool access. This is useful for custom server calling and integration with local LLMs.

### Installation

Install the `mcp-use` package:

```bash
uv add mcp-use
```

### Configuration

Create a file named `weather.json` and add the following configuration to connect local LLMs to the MCP server:

```json
{
  "mcpServers": {
    "weather": {
      "command": "C:\\Users\\gaura\\AppData\\Local\\Programs\\Python\\Python313\\Scripts\\uv.EXE",
      "args": [
        "run",
        "--with",
        "mcp[cli]",
        "mcp",
        "run",
        "C:\\Users\\gaura\\OneDrive\\Desktop\\AI projects\\mcp_project\\server\\weather.py"
      ]
    }
  }
}
```

**Note:** Update the paths in the configuration to match your system paths.

## References

- **FastMCP**: https://github.com/jlowin/fastmcp
  - Create MCP servers and connect them to different clients like Claude, Cursor, etc.

- **mcp-use**: https://github.com/mcp-use/mcp-use
  - Connect to MCP servers directly without an AI agent for programmatic tool access (custom server calling and use)

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

Since there is only one tool, it inherently follows a consistent pattern with itself. The naming uses a verb_noun format (get_alerts), which is clear and standard, and there are no other tools to introduce inconsistency.

Tool Count2/5

A single tool is too few for a weather server, as it severely limits functionality. For a weather domain, agents would expect basic operations like getting current conditions, forecasts, or historical data, but this server only provides alerts for US states, making it incomplete and under-scoped.

Completeness1/5

The tool set is severely incomplete for a weather server. It only covers weather alerts for US states, missing core weather functionalities such as current weather, forecasts, or data for other regions. This creates significant gaps that will likely cause agent failures when broader weather queries are made.

Maintenance

ActivityInactive
ResponsivenessNo issues