Skip to main content Announcing Tool Policies: AI agent permissions down to the field Read the announcement
StackOne
Connectors
Connect

Connect to everything your agents need, without writing the infrastructure to get there.

Secure

Enterprise-grade controls to ensure your agent always meets security & compliance standards.

Optimize

Maximise agent efficiency – faster responses, increased accuracy, fewer tokens used.

For SaaS products Embedded AI agent integrations Give your product's agent every system your customers use.
Pricing
Login
Book Demo Start Free
StackOne
Connectors
Connect

Connect to everything your agents need, without writing the infrastructure to get there.

Secure

Enterprise-grade controls to ensure your agent always meets security & compliance standards.

Optimize

Maximise agent efficiency – faster responses, increased accuracy, fewer tokens used.

Pricing
Book Demo Start Free
Live 6 Actions

Open-Meteo MCP Server
for AI Agents

Connect your AI agent to StackOne's Open-Meteo MCP server and give it ready-to-use MCP tools out of the box. Auth, tool execution, and security all managed.

Start Free Book Demo Read Docs →
Open-Meteo logo
Open-Meteo MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

6 Agent Actions

Read-only access to Open-Meteo. Extend your agent's capabilities with custom actions.

MCP Actions → Build Actions →

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Open-Meteo MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Open-Meteo tool response scanned for prompt injection in milliseconds, with 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Open-Meteo call.

Tools Discovery →

What is the Open-Meteo MCP Server?

A Open-Meteo MCP server lets AI agents read Open-Meteo data through the Model Context Protocol, Anthropic's open standard for connecting LLMs to external tools. StackOne's Open-Meteo MCP server ships with pre-built actions, fully extensible via the Connector Builder, plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Open-Meteo MCP Tools

Every StackOne action for Open-Meteo, ready for your agent. Read-only, scoped to exactly what you need.

Air Qualitys

  • Get Air Quality

    Get air quality data for a location

Locations

  • Search Locations

    Search for locations by name using the geocoding API

Elevations

  • Get Elevation

    Get elevation data for given coordinates

Marine Weathers

  • Get Marine Weather

    Get marine weather forecast data for a location

Weather Forecasts

  • Get Weather Forecast

    Get weather forecast data for a location

Historical Weathers

  • Get Historical Weather

    Get historical weather data for a location and date range

Set Up Your Open-Meteo MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Open-Meteo in under 10 lines of code.

MCP Clients

Claude Desktop setup guide
Claude Code setup guide
Cursor setup guide
Goose setup guide

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More Data Infrastructure MCP Servers

Fivetran

172+ actions

Better Stack

145+ actions

Supabase

138+ actions

New Relic

135+ actions

Statuspage

102+ actions

Grafana

100+ actions

Render

98+ actions

All Data Infrastructure MCP Servers →

Platform Resources

Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery

Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.

10 min

Indirect Prompt Injection Defense for MCP Tools: A Technical Guide

MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.

12 min

MCP vs A2A: Architecture, Security, and When to Use Each

MCP vs A2A: what each protocol standardizes, how they differ, the security risks they share, and when to use one, both or a hybrid.

12 min

MCP vs API: What Hundreds of Connector Builds Taught Us

MCP wraps APIs, it doesn't replace them. After building hundreds of connectors that serve both, here's when each approach wins.

14 min read

Open-Meteo MCP Server FAQ

Does StackOne have a Open-Meteo MCP server?
Yes. StackOne offers a managed Open-Meteo MCP server, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Open-Meteo MCP server vs direct API integration: what's the difference?
A Open-Meteo MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software work, where backend code calls Open-Meteo. A Open-Meteo MCP server is for AI agents that discover and call Open-Meteo at runtime, such as MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI. StackOne provides both.
How does Open-Meteo authentication work for AI agents?
Open-Meteo authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK to get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Open-Meteo account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Open-Meteo MCP tools vulnerable to prompt injection?
Yes. Open-Meteo MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content, such as documents, messages, tickets, records, or free-text fields, is a potential vector. StackOne Defender scans every tool response before it enters the agent's context. It runs regex patterns in ~1ms, then a MiniLM classifier in ~4ms. Accuracy is 88.7%, and it runs entirely on CPU.
What is the context bloat of a Open-Meteo agent and how do I avoid it?
Context bloat happens when Open-Meteo tool schemas and API responses eat your Open-Meteo agent's memory, preventing it from reasoning effectively. A single Open-Meteo query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery reduces it by loading only the tools relevant to each query.
Can I limit which actions my Open-Meteo agent can access?
Yes. You can limit which actions your Open-Meteo agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Open-Meteo MCP server?
Yes. You can create custom agent actions for your Open-Meteo MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Open-Meteo's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Open-Meteo MCP server?
Skip a Open-Meteo MCP server if your integration is purely software-to-software, because direct Open-Meteo API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Open-Meteo actions at runtime.
What AI frameworks and AI clients does the StackOne Open-Meteo MCP server support?
The StackOne Open-Meteo MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

Connect AI to every company system and control what it can do in each one, down to the field.

Start Free Book Demo