Provides weather forecasts and alerts by connecting AI clients to the US National Weather Service API.
Also known as dingw1982/quickstart-resources, quickstart-resources, @dingw1982/mcp-quickstart-ts
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- 116
- Latest version
- 1.0.1
- Last commit
- Sep 9, 2026
- License
- —
What is Weather MCP?
Weather provides weather forecasts and alerts by connecting AI clients to the US National Weather Service API.
Summary generated from the project's README
About Weather MCP server
Accessing US National Weather Service data through an AI assistant is what this server enables. It provides a bridge between LLM clients and official weather information by exposing specific tools for retrieving meteorological data. Developers can use this to build chatbots that understand current weather conditions and safety warnings.
The server operates over stdio and is available in multiple implementations including Python, TypeScript, Go, Rust, and Ruby. It provides two primary tools: get_forecast and get_alerts. To use the provided example clients, an ANTHROPIC_API_KEY is required to power the chat loop, though the connection to the server can be verified without credentials.
This project serves as a functional example for the Model Context Protocol. It demonstrates how to connect a client to a server to allow an AI to call tools and receive structured results. Users can mix and match different languages, such as using a Python client to drive a TypeScript server.
What you can do with it
- 1Verify MCP tool connectivityTest the connection between a client and server without needing an API key.
Written from the project's README. Every use case is checked against a quote from it.
How to install Weather MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Weather MCP in Claude Code
$ claude mcp add --env 'YOUR_API_KEY=<YOUR_YOUR_API_KEY>' quickstart-resources -- npx -y @dingw1982/mcp-quickstart-tsInstall Weather MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"quickstart-resources": {
"command": "npx",
"args": [
"-y",
"@dingw1982/mcp-quickstart-ts"
],
"env": {
"YOUR_API_KEY": "<YOUR_YOUR_API_KEY>"
}
}
}
}Install Weather MCP in VS Code
.vscode/mcp.json
{
"servers": {
"quickstart-resources": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dingw1982/mcp-quickstart-ts"
],
"env": {
"YOUR_API_KEY": "<YOUR_YOUR_API_KEY>"
}
}
}
}Install Weather MCP in VS Code CLI
$ code --add-mcp '{"name":"quickstart-resources","type":"stdio","command":"npx","args":["-y","@dingw1982/mcp-quickstart-ts"],"env":{"YOUR_API_KEY":"<YOUR_YOUR_API_KEY>"}}'Install Weather MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"quickstart-resources": {
"command": "npx",
"args": [
"-y",
"@dingw1982/mcp-quickstart-ts"
],
"env": {
"YOUR_API_KEY": "<YOUR_YOUR_API_KEY>"
}
}
}
}Install Weather MCP in Codex
$ codex mcp add quickstart-resources --env 'YOUR_API_KEY=<YOUR_YOUR_API_KEY>' -- npx -y @dingw1982/mcp-quickstart-tsInstall Weather MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.quickstart-resources] command = "npx" args = ["-y", "@dingw1982/mcp-quickstart-ts"] [mcp_servers.quickstart-resources.env] YOUR_API_KEY = "<YOUR_YOUR_API_KEY>"
Install Weather MCP in Gemini CLI
$ gemini mcp add -s user -e 'YOUR_API_KEY=<YOUR_YOUR_API_KEY>' quickstart-resources npx -- -y @dingw1982/mcp-quickstart-tsInstall Weather MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"quickstart-resources": {
"command": "npx",
"args": [
"-y",
"@dingw1982/mcp-quickstart-ts"
],
"env": {
"YOUR_API_KEY": "<YOUR_YOUR_API_KEY>"
}
}
}
}Configuration
YOUR_API_KEYRequiredSecretYour API key for the service
| Name | Description | |
|---|---|---|
| YOUR_API_KEY | Your API key for the service | RequiredSecret |
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachabledingw1982/quickstart-resources is public and reachablegithub.com/dingw1982/quickstart-resources ↗Pass
- Package names this repository as its source@dingw1982/mcp-quickstart-ts names dingw1982/quickstart-resources as sourcenpmjs.com/package/@dingw1982/mcp-quickstart-ts ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-09-09github.com/dingw1982/quickstart-resources ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @dingw1982/mcp-quickstart-tsPass
- No critical advisory in the package or its dependencies4 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMCP Quickstart Resources
Example servers and clients for the Model Context Protocol (MCP), in five languages. These are companion examples for two official tutorials:
- Build an MCP server – a simple MCP weather server exposing two tools backed by the US National Weather Service API
- Build an MCP client – an LLM-powered chatbot MCP client that connects to any stdio server and lets Claude call its tools
What's in this repository
Each example lives in its own directory with its own README covering prerequisites, setup, and how to run it:
| Language | Weather server (MCP server) | Chatbot (MCP client) |
|---|---|---|
| Python | weather-server-python |
mcp-client-python |
| TypeScript | weather-server-typescript |
mcp-client-typescript |
| Go | weather-server-go |
mcp-client-go |
| Rust | weather-server-rust |
mcp-client-rust |
| Ruby | weather-server-ruby |
mcp-client-ruby |
All servers communicate over stdio and expose the same two tools: get_forecast and get_alerts (or get-forecast and get-alerts in TypeScript).
All clients launch a server, list its tools, and start an interactive chat loop in which Claude can call those tools. The Python, TypeScript, and Ruby clients take a path to a server script; the Go and Rust clients take the command to run, plus any arguments.
Note: These example clients need an ANTHROPIC_API_KEY to operate. Without a key, each client still connects and lists the server's tools before exiting, so you can verify the MCP wiring without credentials.
You can mix and match across languages: for example, the Python client can drive the TypeScript server. Each client's README lists which server launch forms it supports.
The tests directory contains the smoke tests that run in CI against these examples. See tests/README.md for how they work.
Prerequisites
Each example only needs its own language toolchain. To work across the whole repository (for example, to run the smoke tests) you need:
- Node.js 24+ and npm
- Python 3.10+ and uv
- Go 1.25+
- Rust 1.88+ and Cargo
- Ruby 3.4+ and Bundler
Running the tests
./tests/smoke-test.sh
The smoke tests verify that every server starts and answers MCP requests (including validating structured tool results against the schemas each tool advertises), and that the Python, TypeScript, and Ruby clients can connect to a mock server and list tools. They run automatically on every pull request via GitHub Actions.
Contributing
Contributions are welcome. To submit a change:
- Fork the repository and create a branch from
main. - Make your change. Keep the examples minimal - they exist to teach the protocol, not to be production services.
- If you change an example's behavior, setup, or dependencies, update that example's README to match.
- Run
./tests/smoke-test.shand make sure it passes. - Open a pull request against
maindescribing what changed and why.
A few conventions to follow, in line with the broader Model Context Protocol contributing guidelines:
- Keep documentation clear, concise, and technically accurate. Include code examples where appropriate, and test the commands and links you add.
- Disclose AI assistance. If you used any kind of AI assistance to prepare your contribution, say so in the pull request or issue. See AI_POLICY.md for what the disclosure should cover.
- Be respectful. This project follows the MCP community's Code of Conduct. Concerns can be reported to mcp-coc@anthropic.com.
Security note
These examples are intentionally minimal. If you expose an MCP server over a network (HTTP/SSE/WebSocket), add authentication and basic hardening (CORS allowlist, request size limits, timeouts, rate limits, and log redaction). See SECURITY.md.
License
The MCP project is transitioning from the MIT License to Apache-2.0. New code contributions are licensed under Apache-2.0, and documentation (excluding specifications) under CC-BY-4.0. Earlier contributions whose authors have not consented to relicensing remain under the MIT License. See LICENSE for the full terms.
Weather MCP questions
How do I add Weather MCP to Claude Code?
Run claude mcp add --env 'YOUR_API_KEY=<YOUR_YOUR_API_KEY>' quickstart-resources -- npx -y @dingw1982/mcp-quickstart-ts in your terminal. Add --scope user to make it available in every project.
How do I add Weather MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does the weather server expose?
The server exposes two tools: get_forecast and get_alerts.
Does the client require an API key to list tools?
No, you can verify the MCP wiring and list tools without credentials, though an ANTHROPIC_API_KEY is needed for full operation.
Can I use different languages for the client and server?
Yes, you can mix and match languages, such as using a Python client to drive a TypeScript server.