Weather by WindBorne
com.windbornesystemsPublished by windbornesystems.comOfficial publisherv1.0.0Updated Oct 24, 2026
World's most accurate forecasts & insights, powered by WeatherMesh AI & Atlas balloons.
Overview
A remote MCP server from WindBorne Systems that gives an assistant access to its WeatherMesh AI forecasts and weather insights.
- What you can do
- WindBorne Systems describes this server as providing access to its forecasts and insights, powered by WeatherMesh AI and Atlas balloons. It runs as a hosted remote endpoint, so the assistant connects to it directly rather than running anything locally. The manifest does not list individual tools, so the exact set of queries and outputs is not documented here.
- When to use it
- Consider it when you want an assistant to pull weather forecast or weather-related insight into a conversation, and you are willing to connect to WindBorne's hosted service with an account. It is less useful if you need offline access or a documented list of specific tools before installing.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the WindBorne endpoint. Authentication is required via OAuth, so a WindBorne account or authorization flow is needed. No environment variables, headers or local packages are declared.
Installation
In SourceWeft
- Open Weather by WindBorne in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.windbornesystems%2Fweather/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"weather-by-windborne": {
"type": "http",
"url": "https://weather-mcp.windbornesystems.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.