INDIVIDUAL MCP TOOL

list_products

Lists every data product the Forum serves, as the platform's own catalogue answer: slug, title, lifecycle state, price in credits per call (1 credit = $0.

openweathermap.orgnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.openweathermap.org/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_products and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

openweathermap.org

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.forum]
url = "https://mcp.openweathermap.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "forum": {
      "type": "http",
      "url": "https://mcp.openweathermap.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: forum
Remote MCP URL: https://mcp.openweathermap.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "forum": {
      "url": "https://mcp.openweathermap.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "forum": {
      "type": "http",
      "url": "https://mcp.openweathermap.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "forum",
  "transport": "streamable-http",
  "url": "https://mcp.openweathermap.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

get_product — Returns one product by slug: its live catalogue entry (price, licence, lifecycle state, the specification address) together with the routes fetch_data can call and the parameters each route requires, taken from the platform's published product record.
sign_up — Creates a Forum account for an email address under the Terms version currently served (or the tos_version you name), and returns the account, its first key — the secret is shown exactly once — and the 1,000-credit signup grant spendable on any product.
account_status — Reads the account behind the key: tier, accepted Terms version, the products it may call, the one balance in credits (granted plus bought, minus spend), the last 30 days of usage per day, product and key, and the 50 latest balance movements.
get_topup_link — Opens a top-up for the account and returns the payment intent with hosted_url, the payment provider's short-lived page where a human completes the payment — no tool pays, and card details never touch the Forum.
fetch_data — Fetches one data response: GET data.