Weather Edge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weather_signalsA | Get calibrated edge signals for one city's Kalshi weather markets. Args: city: One of nyc, chicago, denver, miami, la. |
| get_all_signalsA | Run a full scan across all supported cities and rank top weather-market signals. |
| get_forecastC | Get raw calibrated forecast context for one supported city. Args: city: One of nyc, chicago, denver, miami, la. |
| get_station_observationB | Get the latest METAR observation from the settlement station for one city. Args: city: One of nyc, chicago, denver, miami, la. |
| list_citiesA | List supported cities, settlement stations, and calibration parameters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RJW34/weather-edge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server