How to integrate Openweather api MCP with DeepSeek Harness

Connect DeepSeek Harness to Openweather api MCP. Get current weather in paris right now, show 5-day forecast for san francisco, and more using natural language, with authentication handled for you.

Openweather api logoOpenweather api
Api Key

Openweather api provides global weather data, forecasts, and climate history. Instantly access accurate, location-based weather insights for any app or workflow.

21 Tools

Introduction

DeepSeek Harness (dsh) is an open-source agent runtime from DeepSeek AI, and every part of it is a plugin, so you can swap out the model adapter, the tool registry, or the agent loop. It runs on the Cordis framework and comes with a local Web UI, a headless CLI runner, and a Python SDK. You can point it at DeepSeek V4-Pro and V4-Flash, or at Anthropic, OpenAI, and other OpenAI-compatible providers. It is MIT licensed and still in developer preview.

This guide shows how to connect your Openweather api account to DeepSeek Harness, and you can do it with either the Composio Connect CLI or the Composio Connect MCP. The dsh-base bundle gives shell execution as a first-class tool, so the CLI is the easiest path for personal use. It is quick to set up and needs no server config, and the MCP path works well too, since the harness comes with a built-in MCP client.

Also integrate Openweather api with

What is Composio Connect?

Composio Connect lets anyone plug 1,000+ applications directly into their agent harness, including DeepSeek Harness, through a single hosted MCP endpoint. Each task runs as a session, a scoped runtime that ties together the user, the available toolkits, authentication, and execution state. It can:

  • Discover and load tools on-demand. A small set of meta tools lets the agent search for the right tool at runtime, so you never load hundreds of tool definitions into context.
  • Chain tools in a sandboxed remote workbench. Multi-step workflows run server-side, passing outputs between tools and working with files in the session's sandbox, so long chains finish without a lot of back-and-forth with the LLM.
  • Manage authentication end-to-end. Managed OAuth, per-user connected accounts, and account isolation are all handled for you, so you never wire up auth yourself.

Connect Openweather api to DeepSeek Harness with Composio

Prerequisites: Install DeepSeek Harness

DeepSeek Harness needs Node.js (20 or 22) and pnpm. Build it from source. This is also what the MCP path in Option 2 requires, since the built-in MCP client resolves its dependencies from the checkout:

bash
git clone https://github.com/deepseek-ai/deepseek-harness.git
cd deepseek-harness
pnpm install
pnpm run build
pnpm dsh web

The Web UI listens on http://127.0.0.1:3080 by default. Open that address to confirm it is up.

Then configure your model route. In the Web UI, open Settings → Models: the built-in DeepSeek card accepts a DeepSeek API key, and the same page supports Anthropic, OpenAI, and custom OpenAI-compatible endpoints. Full first-run details are in the DeepSeek Harness docs.

Option 1: Composio CLI (recommended)

DeepSeek Harness runs shell commands as a first-class tool through its dsh-base bundle, so the Composio Universal CLI fits well. There is no MCP server to configure, and multi-step tool chaining is reliable. Install and authenticate:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Log in to Composio
composio login

Connect to Openweather api

Ask DeepSeek Harness to connect to Openweather api, or just request any Openweather api-related task. Under the hood the agent calls Composio commands like any other shell tool:

bash
composio search "what can I do with Openweather api?"
composio link openweather_api

On the first Openweather api call, composio link openweather_api opens an OAuth prompt so you can authorize access. After that, every Openweather api command works with your stored credentials automatically, so you just talk to the agent and it will search, execute, and chain Openweather api tools as needed.

Option 2: Composio MCP

DeepSeek Harness bridges MCP through its built-in @deepseek-ai/dsh-mcp-client plugin. You register one server as a plugin row, and its tools appear under server-qualified names (mcp__<serverName>__<rawName>), the same shape Claude Code and Codex use.

MCP requires the source build. The built-in client depends on the harness's own internal packages (cordis, dsh-llm, dsh-tools, dsh-invariants, dsh-subprocess), which resolve from the git checkout you built in the prerequisites. Run everything below from that checkout with pnpm dsh. For a route that avoids editing config files, see the community plugin at the end of this section.

Auth note: The built-in client passes static headers only and has no OAuth flow, so authenticate to Composio Connect with the x-consumer-api-key header. For Composio's OAuth flow, use the community plugin below.

1. Register the Composio server

The web profile's user patch layer is $DSH_HOME/profiles/web/cordis.patch.yml ($DSH_HOME defaults to ~/.dsh). This is a patch file, so a new plugin goes under an insert: entry. A bare - id: row instead targets an existing entry and fails to boot with patch: entry "…" not found. Add:

bash
- insert:
    - id: mcp-composio
      name: '@deepseek-ai/dsh-mcp-client'
      config:
        serverName: composio
        transport: streamable-http
        url: https://connect.composio.dev/mcp
        headers:
          x-consumer-api-key: !!js process.env.COMPOSIO_API_KEY

2. Set the API key and launch

The header value must resolve to a string at load time. Export your Composio consumer API key (ck_...), which is on the Connect → Settings → Sessions page of the Composio dashboard, in the shell you launch from. If it is unset, process.env.COMPOSIO_API_KEY is undefined and the config fails validation:

bash
export COMPOSIO_API_KEY=ck_your_key
pnpm dsh web

3. Done!

Open http://127.0.0.1:3080 and start a session on Standard or Code mode. (Minimal mode exposes only bash and str_replace_editor, so it hides MCP tools.) Composio's tools register as mcp__composio__*. Ask DeepSeek Harness to connect to Openweather api or request any Openweather api-related task, and Composio authorizes Openweather api on demand on the first call.

The dsh-mcp-client config schema (transport, serverName, url, headers, plus reconnect.* and toolCallTimeoutMs) is the current developer-preview interface and may change between releases.

Alternative: OAuth via the community plugin

To use Composio Connect's OAuth flow instead of a static key, or to skip editing cordis.patch.yml by hand, use the community dsh-mcp-manager plugin. It installs as a self-contained external plugin, ships a bundle patch so it auto-mounts, and adds a Settings → MCP page plus OAuth (authorization code + PKCE, RFC 7591 dynamic client registration, and refresh-token rotation). It needs the web profile and Node.js ^22.19 or >=24, with pnpm on your PATH.

Install it from your source checkout, then restart pnpm dsh web and refresh:

bash
pnpm dsh plugin --profile web add github:hyqhyq3/dsh-mcp-manager

Open Settings → MCP → + Add MCP server, choose HTTP, set the name to composio, the URL to https://connect.composio.dev/mcp, and the auth mode to OAuth. Click Authenticate, and Composio's login and consent screen opens in the browser, then redirects back and registers the tools as mcp__composio__*. The row should read connected (N tools).

The plugin catches the OAuth code on a loopback redirect (http://127.0.0.1:<port>/mcp-manager/callback/<id>), so Composio's OAuth provider must allow that loopback URL. Server configs and tokens persist at ~/.dsh/mcp-manager.json, so treat that file as a secret. Being a community plugin on a preview harness, its commands may change, so check the plugin repo if a step drifts.

What is the Openweather api MCP server, and what's possible with it?

The Openweather api MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Openweather api account. It provides structured and secure access to real-time, forecasted, and historical weather data, so your agent can fetch current conditions, deliver forecasts, analyze air quality, and perform location-based weather insights on your behalf.

  • Current weather retrieval: Instantly get up-to-the-minute weather details for any city or geographic coordinate, including temperature, humidity, and wind.
  • Five-day weather forecasting: Ask your agent for detailed 5-day forecasts in 3-hour intervals to plan events, travel, or outdoor activities.
  • Air pollution and UV index analysis: Retrieve current, forecasted, and historical air pollution data, as well as UV index values, to monitor environmental quality for any location.
  • Geocoding and reverse geocoding: Convert location names to coordinates or find city/state information from latitude and longitude, enabling location-aware weather queries.
  • Radius-based weather search: Fetch weather conditions for all cities within a specified radius around a geographic point for broader regional analysis.

Way Forward

With Openweather api connected, DeepSeek Harness can now act on your behalf whenever you ask it to.

From here, you can extend the harness further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup, and each new integration adds to what your agent can do for you.
  • Build workflows across tools: Once multiple apps are connected, DeepSeek Harness can chain actions together, so it can turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Use the plugin system: Wrap common Openweather api flows as dsh plugins or prompt templates so recurring tasks become one-line commands, and bundle your most-used Openweather api tools into a named profile you can boot on demand.

If you run into trouble or want to share what you've built, join the community or check out the Docs for more configuration options.

TOOLS

Supported Tools

Every Openweather api action and event your agent gets out of the box.

Delete Weather Station

Tool to delete a registered weather station.

Get 5 Day Forecast

Tool to get a 5-day forecast every 3 hours (up to 40 UTC timestamps).

Get Current Air Pollution Data

Tool to fetch current air pollution data for a location.

Get Air Pollution Forecast

Tool to get forecasted air pollution data for a specific location.

Get Air Pollution History

Tool to retrieve historical air pollution data.

Get Circle City Weather

Tool to search for current weather data in cities around a geographic point.

Get Current Weather

Tool to retrieve current weather data for a location.

Get Geocoding by Zip Code

Tool to convert zip/post code into geographic coordinates.

Get Direct Geocoding

Tool to convert a location name into geographic coordinates.

Get Reverse Geocoding

Tool to convert geographic coordinates into a location name.

Get Station Measurements

Tool to retrieve aggregated measurements from a weather station with minute, hour, or day granularity.

Get Current UV Index

Tool to retrieve current UV index for a location.

Get UV Index Forecast

Tool to retrieve UV index forecast for a specific location.

Get UV Index History

Tool to retrieve historical UV index data for a specified location and time range.

Get Weather Map Tile (2.0)

Tool to fetch Weather Maps 2.

Get Weather Station

Tool to get information about a specific weather station by its ID.

Get Weather Stations

Tool to list all weather stations added to your account.

Get Weather Triggers

Tool to retrieve weather triggers for specific conditions.

Add Weather Station

Tool to add a new weather station to your account.

Submit Station Measurements

Tool to submit weather measurements from a registered station.

Update Weather Station

Tool to update weather station details.

FAQ

Frequently asked questions

With a standalone Openweather api MCP server, the agents and LLMs can only access a fixed set of Openweather api tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Openweather api and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. DeepSeek Harness fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Openweather api tools.

Yes, absolutely. You can configure which Openweather api scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Openweather api data and credentials are handled as safely as possible.

Start with Openweather api.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Openweather api tool your agent needs.Free to start.

Start building