MCP US Weather Client/Server

Created By
ankitmishralivea year ago
A simple MCP (Model Context Protocol) server that provides weather alert information for US states, leveraging the National Weather Service (NWS) API. It also includes an example client application that demonstrates how to interact with the MCP server using the mcp_use library.
Overview

What is Hands-on-MCP?

Hands-on-MCP is a project that implements a Model Context Protocol (MCP) server to provide weather alert information for US states, utilizing the National Weather Service (NWS) API. It includes a client application that demonstrates interaction with the MCP server using the mcp_use library.

How to use Hands-on-MCP?

To use Hands-on-MCP, clone the repository, install the necessary dependencies, set up your environment variables, and run the server and client applications. You can interact with the client by typing queries related to weather alerts.

Key features of Hands-on-MCP?

  • Fetches and formats active weather alerts for specified US states.
  • Demonstrates MCP server construction using the fastmcp library.
  • Provides a client application that integrates conversation memory.
  • Showcases integration with Langchain for LLM interactions.

Use cases of Hands-on-MCP?

  1. Fetching real-time weather alerts for different states.
  2. Demonstrating the use of MCP in client-server architecture.
  3. Integrating weather data into applications using the NWS API.

FAQ from Hands-on-MCP?

  • What programming language is used?

    The project is implemented in Python.

  • Do I need an API key?

    Yes, a Groq API key is required and should be added to the .env file.

  • How do I run the server and client?

    Use the command uv run mcp dev server/weather.py to start the server and uv run server/client.py to start the client.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ankitmishralive
Star
0
Language
Python
License
-

Recommend Servers

View All
Mnemom

14 hours ago
//beforeyouship — LLM Cost Modeling From Your Editor
@Indiegoing

Query realistic LLM cost models without leaving your editor. beforeyouship models the **true monthly cost** of an LLM app architecture — retries, prompt caching, batch discounts, infra overhead, and 3×/10× growth — across GPT-5.x, Claude, Gemini, DeepSeek, and more. Not a token calculator: a planning tool for the design phase, before you commit to a stack. **No API key needed to try it** — demo mode covers the six free-tier models. A Pro key from [beforeyouship.dev](https://beforeyouship.dev) unlocks the full 18-model catalog. ## What you can ask - "How much will a RAG chatbot cost at 10,000 requests/day?" - "Compare Claude Haiku vs Gemini Flash pricing for my workload" - "What's the cheapest model for a multi-step agent at scale?" - "Show me current per-token prices for Anthropic models" ## Tools ### `estimate_cost` Full cost model for an architecture at a given usage level. Returns Naive / Realistic / Worst Case monthly cost per model, 3×/10× growth scenarios, and an opinionated recommendation with reasoning. ### `get_model_prices` Current per-1M-token pricing — input, output, cached input, batch — with context windows and staleness metadata. ### `list_archetypes` Seven preset architecture patterns (simple chatbot, chatbot with history, RAG pipeline, multi-model router, coding assistant, document processor, multi-step agent) used as starting points for estimates. ## Setup **Claude Code:** ​```bash claude mcp add --transport http beforeyouship https://beforeyouship.dev/api/mcp ​``` **Cursor / other clients** — add a remote server: ​```json { "mcpServers": { "beforeyouship": { "type": "streamable-http", "url": "https://beforeyouship.dev/api/mcp" } } } ​``` Add an `Authorization: Bearer bys_...` header with a Pro key for the full catalog. ## Try it > Estimate the monthly cost of a RAG pipeline at 10,000 requests/day

13 hours ago
Docwand

13 hours ago