Visualcrossing

What Visualcrossing does

Visualcrossing exposes weather data from the Visual Crossing Weather Timeline API to MCP-compatible clients. Its three dedicated tools cover different time ranges:

• weather_timeline retrieves daily weather for a location. It supports historical dates, future dates, and date ranges. A single start_date requests one day; adding end_date requests a range. Results include daily temperature, minimum and maximum temperature, humidity, precipitation, wind, and conditions.
• current_conditions returns live conditions for a location, including temperature, feels-like temperature, humidity, wind, and conditions.
• forecast returns the upcoming 15 days of daily weather, with temperature ranges, humidity, precipitation chance, wind, and conditions.

This makes the server suitable for agents answering location-based weather questions, comparing conditions across dates, or retrieving forecast details for planning.

How it works

The hosted connection uses the Pipeworx gateway endpoint at https://gateway.pipeworx.io/visualcrossing/mcp. A client can connect to that URL as an MCP server. The gateway also offers direct HTTP access to individual tools; for example, POST /v1/tools/weather_timeline accepts a JSON body containing location, start_date, and optionally end_date.

The npm package, @pipeworx/mcp-visualcrossing, runs as a local stdio bridge. The MCP client starts it with npx, and the bridge forwards requests to the hosted gateway, so it requires network access and has no offline mode.

The gateway endpoint also exposes shared Pipeworx meta-tools. The local package lists only the Visualcrossing tools by default; setting PIPEWORX_META_TOOLS=1 adds tools such as ask_pipeworx, discover_tools, search_within, remember, and recall. ask_pipeworx can select a tool and populate its arguments from a natural-language question.

Setup and configuration

For a hosted MCP connection, add the endpoint to the client's MCP configuration:

{
  "mcpServers": {
    "visualcrossing": {
      "url": "https://gateway.pipeworx.io/visualcrossing/mcp"
    }
  }
}

For the local bridge, configure the command and package instead:

{
  "mcpServers": {
    "visualcrossing": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-visualcrossing"]
    }
  }
}

Anonymous use is available for the first calls and is limited to 50 calls per day. A free Pipeworx account and PIPEWORX_API_KEY increase the allowance to 200 calls per day. The key is passed as a Bearer token, and calls are metered and billed in the same way as hosted connections. When using an HTTPS proxy, newer Node.js releases may require NODE_USE_ENV_PROXY=1 because Node's built-in fetch does not otherwise read HTTPS_PROXY by default.

Limitations and notes

The local bridge depends on network connectivity. The hosted and local connections use the Pipeworx gateway rather than connecting directly from the MCP client to Visual Crossing. A pack-specific endpoint includes shared gateway meta-tools in addition to the weather tools, while the local bridge can hide those tools unless explicitly enabled. The gateway also provides a full endpoint at https://gateway.pipeworx.io/mcp when direct access to all available packs is preferred.

Visualcrossing is an independent, unofficial integration and is not affiliated with, endorsed by, or published by Visual Crossing.