This MCP server exposes real-time weather data for requested cities in a standardized MCP format so Claude and other MCP-compatible agents can query it and receive structured weather information. The server retrieves current conditions such as temperature, humidity, and a concise weather condition description. Clients can request weather data for a city by addressing the MCP endpoint defined by the server and parsing the returned model-context data. The design follows the MCP protocol conventions to ensure interoperability with Claude-enabled agents and any other MCP clients.

To use the tools, connect to the weather MCP endpoints exposed by this server. Provide a city name (and optional parameters like units or language, if supported) and receive a structured response containing: the current temperature, humidity, weather condition description, and metadata such as timestamp and data source. The server is intended to be a drop-in weather data provider for MCP workflows, enabling agents to reason about or plan actions based on real-time weather context.

Prerequisites:

• Node.js (v14+ or current LTS)
• npm or pnpm
• Access to a weather data provider API (required API key)

1. Clone the repository git clone https://github.com/your-org/phoenixxxtm-claude-mcp-server.git cd phoenixxxtm-claude-mcp-server

2. Install dependencies npm install

3. Configure environment

   • Create a .env file or export environment variables: WEATHER_API_KEY=your-api-key-here WEATHER_API_BASE_URL=https://api.weatherprovider.example/v1

4. Run the server npm run start

   or if a direct node command is used elsewhere:

   node server.js

5. Verify the MCP endpoint

   • Send a standard MCP query to the server's endpoint for a city, e.g., /mcp/weather?city=London
   • Expect a response containing temperature, humidity, and condition data in MCP-compliant JSON format.

Environment variables are required for the external weather data provider. If you encounter authentication errors, double-check the WEATHER_API_KEY and ensure the API key has permissions for the requested endpoints. If the base URL changes, update WEATHER_API_BASE_URL accordingly. For debugging, enable verbose logging in the environment (e.g., LOG_LEVEL=debug) if supported by the server. Ensure the server has network access to the weather API and that rate limits are considered for high-traffic usage. The MCP data model should be consistent with the MCP specification for model-context data exchange.