
AccuWeather MCP
- Updated June 11, 2026
- JonJam/accuweather-mcp
AccuWeather MCP is a MCP server that exposes AccuWeather-sourced weather tools to AI coding agents over stdio.
About
AccuWeather MCP is a small Model Context Protocol server that wraps AccuWeather data as tools your coding agent can call during implementation. developers shipping dashboards, travel assistants, outdoor apps, or notification prototypes register the server in Claude Code, Cursor, or Windsurf, set ACCUWEATHER_API_KEY, and pull forecasts and conditions into prompts instead of tab-hopping. The catalog lists it under Build → Integrations because the payoff is wiring a reliable weather provider into your product or agent workflow. It assumes you already have an AccuWeather developer key and a host that supports stdio MCP; it does not replace product design, caching strategy, or compliance review for location data. Compared to scraping or hard-coding static copy, this keeps answers current and traceable to a named API.
- AccuWeather-backed MCP tools exposed over stdio for agent hosts
- Docker OCI package docker.io/jonjam/accuweather-mcp:1.4.9 with pinned server schema
- Requires ACCUWEATHER_API_KEY as a secret environment variable
- GitHub source at JonJam/accuweather-mcp for audit and version 1.4.9
- MCP integration pattern—not a standalone weather app or cron job
AccuWeather MCP by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add AccuWeatherMCP -- npx -y JonJam/accuweather-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Last updated | June 11, 2026 |
|---|---|
| Repository | JonJam/accuweather-mcp ↗ |
What it does
Give Claude Code or Cursor live AccuWeather lookups so your agent can answer location forecasts without you copying data from a browser.
Who is it for?
Best when you're adding weather widgets, trip planners, or alert logic and already have an AccuWeather API key and MCP-capable tooling.
Skip if: Skip if you need free-tier weather without paid API keys, offline-only apps, or full production observability around rate limits.
What you get
After you register the server and set ACCUWEATHER_API_KEY, your agent can query AccuWeather-backed tools directly inside the IDE session.
- Registered MCP server the agent can invoke for weather lookups
- Repeatable env-based auth for AccuWeather inside your dev workflow
By the numbers
- Server version 1.4.9
- Single required secret: ACCUWEATHER_API_KEY
- Package transport: stdio via OCI docker.io/jonjam/accuweather-mcp:1.4.9
README.md
accuweather-mcp
Setup
- Define the following environment variables in your system
export ACCUWEATHER_API_KEY=replace-with-your-api-key
- Define a
application-local.yamlinsrc/main/resources/application.yamlwith the following content:
logging:
console:
enabled: true
- If using Cursor, add the following documentation sources:
- Spring AI documentation
- [Wiremock documentation][https://wiremock.org/docs/]
- [Lombok documentation][https://projectlombok.org/features/]
- PIT documentation
- gradle-pitest-plugin documentation
Run
- Run with
SPRING_PROFILES_ACTIVE=local ./gradlew bootRun
Testing
Note: If you enable the Java debugger, it will produce output to standard out which will trigger errors in the stdio MCP protocol.
Unit and integration testing
Unit and integration tests use mockito and wiremock. To run the tests, use:
./gradlew build
Mutation testing
This project uses PIT mutation testing via the gradle-pitest-plugin to verify that tests detect injected faults, complementing JaCoCo line coverage.
./gradlew pitest— run mutation tests overcom.jonjam.accuweathermcp.*(excluding DTOs and the bootstrap class).- Open
build/reports/pitest/index.htmlto review results. Surviving mutants indicate code that is executed by tests but where a fault would not be caught.
MCP Inspector
To test with MCP Inspector, run the following from the root of the repo:
npx @modelcontextprotocol/inspector -e 'JAVA_TOOL_OPTIONS=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005' java -jar "build/libs/accuweather-mcp-local-snapshot.jar"
This was sourced from this blog.
AI chat (Claude, Cursor)
- Add this configuration to the MCP settings:
{
"mcpServers": {
"accuweather-mcp": {
"command": "PATH_TO_JAVA",
"args": ["-jar", "ABSOLUTE_PATH_TO_REPO/build/libs/accuweather-mcp-local-snapshot.jar"],
"env": {
"ACCUWEATHER_API_KEY": "API_KEY"
}
}
}
}
If you are using SDKMAN, command should be ~/.sdkman/candidates/java/current/bin/java
This was sourced from the MCP docs.
Example user prompt:
Use the accuweather-mcp to look up the current weather in Manchester, UK.
Docker
This project uses the Jib Gradle plugin to build a Docker image.
- Build and load the image into your local Docker daemon:
./gradlew jibDockerBuild
The default image name is jonjam/accuweather-mcp.
To use the docker image with MCP Inspector, the command looks as follows:
npx @modelcontextprotocol/inspector docker run --rm -i --env "ACCUWEATHER_API_KEY=$ACCUWEATHER_API_KEY" jonjam/accuweather-mcp:latest
Patterns and practies
More information about patterns and practises for this project can be found in AGENTS.md.
Git
This project uses semantic-release to automate versioning, changelog generation, and publishing.
Important: Commit messages that are intended to trigger a release must be prefixed according to the Conventional Commits standard. For example:
feat: add new forecast endpointfix: correct hourly forecast time calculation
Spotless
This project uses the Spotless Gradle plugin to enforce a consistent Java style.
./gradlew spotlessApply— format sources and fix style issues../gradlew spotlessCheck— verify formatting without changing files.
Checkstyle
Static analysis and broader code-quality checks are handled by Checkstyle using a Google-style-based configuration (with formatting delegated to Spotless):
./gradlew checkstyleMain— run Checkstyle over main sources../gradlew checkstyleTest— run Checkstyle over test sources.
MCP
- Tools Ensure to handle errors (i.e. validation) according to the specification
MCP Registry
This server is published to the MCP Registry.
When using an MCP client that supports the registry (e.g. Cursor, Claude Desktop), you can add io.github.jonjam/accuweather-mcp from the registry and configure your AccuWeather API key as the ACCUWEATHER_API_KEY environment variable.
Future improvements
- Improve error handling in gateway classes based upon AccuWeather status codes
- Add in-memory caching for AccuWeather API calls that caches data according to expires header
- Add ability to specify desired metric (i.e. Celsius or Fahrenheit) in Tools
- End to end integration tests based on Spring AI Examples
Recommended MCP Servers
How it compares
stdio MCP weather bridge, not a hosted SaaS dashboard or a Claude skill markdown playbook.
FAQ
Who is AccuWeather MCP for?
Developers and small teams using Claude Code, Cursor, or similar hosts who want AccuWeather data available as MCP tools while they integrate weather into apps or agents.
When should I use AccuWeather MCP?
Use it during Build when you are implementing features that need current or forecast weather and you want the agent to fetch data instead of you pasting screenshots or JSON by hand.
How do I add AccuWeather MCP to my agent?
Add the server to your host MCP config, run the published OCI image or equivalent stdio entrypoint, and set the required secret ACCUWEATHER_API_KEY before restarting the client.