OpenMeteo SDK

Open Meteo client, generated from the OpenAPI spec.

This is an unofficial SDK for the Open Meteo public API, generated by Voxgig with @voxgig/sdkgen. It is not affiliated with, endorsed by, or sponsored by the upstream API provider.

TypeScript, Python, PHP, Golang, Ruby, Lua SDKs, a CLI, an interactive REPL, and an MCP server for AI agents — all generated from one OpenAPI spec by @voxgig/sdkgen.

Entities, not endpoints

This SDK exposes the API as a small set of semantic entities — Historical, MarineForecast and WeatherForecast — that you call directly, instead of assembling URL paths and query strings. Entities are Capitalised to mark them as the primary surface, each with the operations they support (load):

const client = new OpenMeteoSDK()
const historical = await client.Historical().load()

Thinking in entities keeps the mental model small — for people and AI agents alike — rather than reasoning about raw HTTP routes and query parameters.

Packages

Quickstart

TypeScript

import { OpenMeteoSDK } from '@voxgig-sdk/open-meteo'

const client = new OpenMeteoSDK({
  apikey: process.env.OPEN_METEO_APIKEY,
})

// Load historical data (returns a Historical)
const historical = await client.Historical().load()
console.log(historical)

See the TypeScript README for the full guide.

Surfaces

Use it from an AI agent (MCP)

The generated MCP server exposes every operation in this SDK as an MCP tool that Claude, Cursor or Cline can call directly. Build and register it:

cd go-mcp && go build -o open-meteo-mcp .

Then add it to your agent’s MCP config (Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "open-meteo": {
      "command": "/abs/path/to/open-meteo-mcp"
    }
  }
}

Entities

The API exposes 3 entities:

The operations available across these entities are load — see each entity’s own list above for exactly which it supports.

Quickstart in other languages

Python

import os
from openmeteo_sdk import OpenMeteoSDK

client = OpenMeteoSDK({
    "apikey": os.environ.get("OPEN_METEO_APIKEY"),
})


# Load a specific historical (returns the record, raises on error)
historical = client.Historical().load()
print(historical)

PHP

<?php
require_once 'openmeteo_sdk.php';

$client = new OpenMeteoSDK([
    "apikey" => getenv("OPEN_METEO_APIKEY"),
]);


// Load a specific historical (returns the bare record; throws on error)
$historical = $client->Historical()->load();
print_r($historical);

Golang

import sdk "github.com/voxgig-sdk/open-meteo-sdk/go"

client := sdk.NewOpenMeteoSDK(map[string]any{
    "apikey": os.Getenv("OPEN_METEO_APIKEY"),
})

// Load historical data
historical, err := client.Historical(nil).Load(map[string]any{}, nil)
fmt.Println(historical)

Ruby

require_relative "OpenMeteo_sdk"

client = OpenMeteoSDK.new({
  "apikey" => ENV["OPEN_METEO_APIKEY"],
})


# Load a specific historical (returns the bare record; raises on error)
historical = client.Historical.load()
puts historical

Lua

local sdk = require("open-meteo_sdk")

local client = sdk.new({
  apikey = os.getenv("OPEN_METEO_APIKEY"),
})


-- Load a specific historical
local historical, err = client:Historical():load()
print(historical)

Unit testing in offline mode

Every SDK ships a test mode that swaps the HTTP transport for an in-memory mock, so unit tests run offline.

TypeScript

const client = OpenMeteoSDK.test()
const historical = await client.Historical().load()
// historical is a bare Historical populated with mock data
console.log(historical)

Python

client = OpenMeteoSDK.test()
historical = client.Historical().load()
print(historical)

PHP

// Seed fixture data so offline calls resolve without a live server.
$client = OpenMeteoSDK::test([
    "entity" => ["historical" => ["test01" => []]],
]);
$historical = $client->Historical()->load();

Golang

client := sdk.Test()
result, err := client.Historical(nil).Load(
    nil, nil,
)

Ruby

# Seed fixture data so offline calls resolve without a live server.
client = OpenMeteoSDK.test({
  "entity" => { "historical" => { "test01" => {} } },
})
historical = client.Historical.load()

Lua

local client = sdk.test()
local result, err = client:Historical():load()

Direct and prepare

For endpoints the entity model doesn’t cover, use the low-level methods:

• direct(fetchargs) — build and send an HTTP request in one step.
• prepare(fetchargs) — build the request without sending it.

Both accept a map with path, method, params, query, headers, and body. See the How-to guides below.

How-to guides

Make a direct API call

When the entity interface does not cover an endpoint, use direct:

TypeScript:

const result = await client.direct({
  path: '/api/resource/{id}',
  method: 'GET',
  params: { id: 'example' },
})
if (result instanceof Error) {
  throw result
}
console.log(result.data)

Python:

result = client.direct({
    "path": "/api/resource/{id}",
    "method": "GET",
    "params": {"id": "example"},
})

PHP:

$result = $client->direct([
    "path" => "/api/resource/{id}",
    "method" => "GET",
    "params" => ["id" => "example"],
]);

Go:

result, err := client.Direct(map[string]any{
    "path":   "/api/resource/{id}",
    "method": "GET",
    "params": map[string]any{"id": "example"},
})

Ruby:

result = client.direct({
  "path" => "/api/resource/{id}",
  "method" => "GET",
  "params" => { "id" => "example" },
})

Lua:

local result, err = client:direct({
  path = "/api/resource/{id}",
  method = "GET",
  params = { id = "example" },
})

Advanced

Everyday use only needs the sections above. This explains the internals behind every call — relevant when writing custom features.

Every SDK call runs the same five-stage pipeline:

1. Point — resolve the API endpoint from the operation definition.
2. Spec — build the HTTP specification (URL, method, headers, body).
3. Request — send the HTTP request.
4. Response — receive and parse the response.
5. Result — extract the result data for the caller.

A feature hook fires at each stage (e.g. PrePoint, PreSpec, PreRequest), so features can inspect or modify the pipeline without forking the SDK.

Features

Pass custom features via the extend option at construction time.

Per-language documentation

• TypeScript
• Python
• PHP
• Golang
• Ruby
• Lua

Upstream API

This SDK is generated from the upstream OpenAPI specification. It is an unofficial client and is not affiliated with the API provider.

• Upstream API: https://open-meteo.com/en/docs

Security

Please report security issues to security@voxgig.com. See SECURITY.md. Do not open public issues for suspected vulnerabilities.

Generated from the Open Meteo OpenAPI spec by @voxgig/sdkgen.