QWeather Tide API MCP for AI. Get precise water levels for any global coast.

Q: How do I make sure the QWeather Ocean/Tide API is working before I run a query?

You use the checkapistatus tool. This runs an immediate, lightweight check to confirm the service is operational. Always call this first; it saves you time if the API is down.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

QWeather Ocean/Tide API gives your AI agent access to real-time, global oceanographic data. It retrieves comprehensive tide tables, pinpoints high and low water peaks by coordinates, and provides detailed metadata needed for marine research or coastal planning.

Use it when you need precise water level metrics, not just general weather forecasts.

What your AI can do

Check api status

Runs a quick check to confirm the QWeather Ocean service is currently operational and ready for requests.

Get ocean tide data

Retrieves real-time tide tables, including high/low peaks, for a specific location ID and date.

Retrieve Tide Tables

Gets a complete, timestamped schedule of water levels for a specific geographic location and date.

Audit Water Peaks

Identifies the precise times and heights when the tide reaches its highest (high tide) or lowest (low tide) point.

Query by Coordinates

Retrieves water level data using latitude and longitude, allowing for highly specific regional audits.

Check Service Status

Validates the live operational status of the QWeather API before running any major data requests.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

QWeather Ocean/Tide API MCP Server: 2 Tools for Maritime Data

These two tools let your AI client access real-time tide tables and verify the operational health of the QWeather oceanography service.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using QWeather Ocean/Tide API on Vinkius

Check Api Status

Runs a quick check to confirm the QWeather Ocean service is currently operational and ready for requests.

Get Ocean Tide Data

Retrieves real-time tide tables, including high/low peaks, for a specific location...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The QWeather Tide API integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "qweather-oceantide-api": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the QWeather Tide API tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"qweather-oceantide-api": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with QWeather Ocean/Tide API, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by QWeather. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 2 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Trying to plan a maritime operation usually means bouncing between three different websites and spreadsheets.

Right now, figuring out when a dock is accessible requires opening the port authority site, then switching to Google Maps for coordinates, and finally finding a separate tide chart service. You spend twenty minutes copying numbers into Excel just to find one reliable high-water window.

With the QWeather Ocean/Tide API, you don't do that anymore. Your agent handles the entire process: it takes your natural language request ('When can we safely dock at this location?') and pulls the exact data from `get_ocean_tide_data`—giving you a single, reliable answer.

The QWeather Ocean/Tide API MCP Server: Getting precise tide metrics in seconds.

Before, checking the status meant logging into a separate dashboard and manually verifying the service was online. If that portal was down for maintenance, your whole project stopped until someone manually notified you.

Now, you just ask your agent to run `check_api_status`. It's an immediate health check. You get confirmation—a simple yes or no—that lets you proceed with confidence, every single time.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

Yo. This QWeather Tide API gives your AI agent direct access to global oceanographic data. You don't wanna manually check some bunch of maritime websites; you just let your agent pull the numbers straight up.

Before running any big request, you gotta run check_api_status. That tool runs a quick confirmation check to make sure the QWeather Ocean service is actually live and ready for data requests. It validates the API's operational status before you waste time on major queries.

The core function lives in get_ocean_tide_data. This tool lets your agent pull real-time tide tables, pinpointing high and low water peaks using a specific location ID and date. You can feed it a location ID and a date to get a complete, timestamped schedule of what the water levels are doing at that spot.

It doesn't just give you average numbers; it maps out the entire cycle.

When you need highly granular data, get_ocean_tide_data accepts coordinates too. You can feed it latitude and longitude to run a localized audit on the water level changes for any specific region. This means you get precise metrics whether your target is defined by an established location ID or by raw geographic markers.

The tool identifies high tide—the absolute peak time and height when the ocean swells up highest—and low tide, flagging those exact times and heights too. It handles both types of peaks within the same data pull, letting you map out temporal patterns for coastal planning or deep marine research.

When your agent pulls this data, it gives you a complete picture: the initial service status confirmation, followed by the full tide table retrieval, and finally, the detailed breakdown of every high and low water event. You get precise metrics that go way beyond general weather forecasts. It's all about specific water level measurements.

Your agent handles the complexity; you just ask for the data.

Built · Hosted · Managed by Vinkius QWeather Tide API - Monitor Ocean Tides and Water Levels

Server ID 019d8474-1f40-73b7-b032-cbc8dccc592b

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is: you confirm system health, then you get the precise environmental numbers.

Subscribe to the server and input your unique QWeather API Key.

Your AI client calls check_api_status first. This confirms the service is online and ready for use.

The agent then uses get_ocean_tide_data, passing the required location coordinates/ID and date to pull the actual water level data.

Who is this actually for?

This API serves anyone whose job depends on accurate, real-time water level data. It's for Marine Researchers needing to verify historical tide patterns; Harbor Masters planning vessel movements; and Coastal Planners who need rapid audits of water peaks for infrastructure projects.

Marine Researcher

Uses get_ocean_tide_data to cross-reference known oceanographic markers, ensuring data accuracy without manual searches.

Port Operations Lead

Runs the API through a workflow agent to automate scheduling and predict optimal loading/unloading windows based on predicted water heights.

Coastal Planner

Queries specific regional data using coordinates to model how changing tide levels affect coastal structures or runoff patterns.

What Changes When You Connect

Pinpoint high and low water events instantly. By querying the data with get_ocean_tide_data, you get the exact height and time of every peak, which is critical for logistics planning.

Verify service uptime first. Running check_api_status before making a complex query saves time and prevents workflow failures when external services are down.

Stay focused on data, not dashboards. Instead of clicking through multiple tabs to find tide charts, your agent handles the location ID lookup and data retrieval in one go.

Model regional changes with precision. You can pass coordinates directly into get_ocean_tide_data, allowing you to audit specific sections of coastline that matter for development.

Process complex time series easily. The API returns full tide tables, giving you timestamped entries for every water level change throughout the entire day.

See it in action

01 01

Planning a deep-sea survey route

The survey team needs to know when the water is deepest. They ask their agent: 'What's the tide forecast for coordinates 34.05, -118.24 on June 1st?' The agent uses get_ocean_tide_data and reports back a clear schedule of high-water peaks, allowing them to adjust their route accordingly.

02 02

Auditing port expansion logistics

The planner needs to know if the current tide levels are sufficient for crane operation. They first run check_api_status to confirm service health, then use get_ocean_tide_data with a specific location ID to confirm minimum water height requirements.

03 03

Investigating historical flooding patterns

A researcher wants to compare current data against past records. They use the API's ability to query by date in get_ocean_tide_data to build a comprehensive, time-stamped dataset for their paper.

04 04

Emergency response coordination

An operations lead needs immediate water level data during an event. They prompt: 'Check the tide status at this harbor immediately.' The agent uses check_api_status and then calls get_ocean_tide_data to give a rapid, reliable assessment.

The honest tradeoffs

Assuming general weather data is enough

Anti-pattern

Thinking that checking the local forecast for 'high water' is sufficient. General weather APIs only provide rough estimates and lack precise timing or height metrics.

The Fix

Always use get_ocean_tide_data. It provides specific tide tables, giving you measured high and low points rather than just a general warning.

Ignoring service status checks

Anti-pattern

Running complex queries like 'Get all data for Shanghai' without verifying the API is up. This leads to vague failure messages or hard stops.

The Fix

Start every session by calling check_api_status. It ensures your workflow doesn't fail just because the external service had a temporary hiccup.

Using general coordinates incorrectly

Anti-pattern

Just typing in two random numbers for latitude and longitude without knowing if they are properly formatted or validated by the server.

The Fix

Use get_ocean_tide_data with confirmed location IDs or precise, verified coordinates to guarantee the data point you're getting is what you think it is.

When It Fits, When It Doesn't

Use this API if your core problem involves water movement—tides, levels, and peaks. Think port logistics, coastal engineering, or marine biology. You need precise metrics: 'How high was the water at 3 PM on May 10th?'

Don't use it if you just need general weather data (like wind speed or temperature) or financial records. For generalized environmental monitoring, look for dedicated meteorological APIs. If your goal is to track inventory movements in a warehouse, skip this and go find an asset management tool.

The key distinction: This server only cares about the water level's rhythm. Use check_api_status first, then use get_ocean_tide_data for any specific environmental data you need.

Questions you might have

How do I make sure the QWeather Ocean/Tide API is working before I run a query? +

You use the check_api_status tool. This runs an immediate, lightweight check to confirm the service is operational. Always call this first; it saves you time if the API is down.

Does `get_ocean_tide_data` support coordinates or just location IDs? +

It supports both. You can pass either a specific Location ID or precise geographic coordinates (latitude/longitude) to get data for the correct spot.

What kind of water level information does `get_ocean_tide_data` provide? +

It provides full tide tables, which means you get timestamped entries for all water level changes throughout the day. You can pinpoint high and low peaks.

If I need data from next month, can `get_ocean_tide_data` handle it? +

Yes, as long as you provide a valid future date in your request parameters, the tool will retrieve the predicted tide tables for that time.

How does using `get_ocean_tide_data` handle API key management for my AI client? +

You must provide your QWeather API Key during server setup. The agent uses this key to authorize every request, ensuring data integrity and tracking usage against the account limits you configured.

If I run complex queries with `get_ocean_tide_data` repeatedly, are there rate limits? +

Yes, the service enforces standard API rate limits. If your agent exceeds the allowed calls per minute or day, subsequent requests will fail with a specific error code. You'll need to check your QWeather account dashboard for current quotas.

What structured format does `get_ocean_tide_data` return so my AI client can use it? +

The tool returns all data as standardized JSON objects. This structure makes the water level metrics, timestamps, and peak information immediately consumable by your agent's logic for scripting or further analysis.

Beyond specific dates, what generalized oceanographic metadata does `get_ocean_tide_data` access? +

The API provides detailed oceanographic metadata alongside tide tables. This helps you perform deep-dive coastal classification and understand broader regional trends that aren't tied to a single day's water level reading.

How do I find my QWeather API Key? +

Log in to your QWeather Developer portal, create a project, and you will find your API Key in your dashboard. Copy and paste it below.

Does it support coordinate search? +

Yes. You can provide location coordinates (lat,lon) to the get_ocean_tide_data tool to retrieve precise regional tide metadata.

What data format is returned for tide tables? +

The API returns detailed hourly or daily tide tables, including timestamped water height and peak type metadata.

Connect to your AI in seconds.

Check api status

Get ocean tide data

QWeather Ocean/Tide API MCP Server: 2 Tools for Maritime Data

Make your AI actually useful.

Check Api Status

Get Ocean Tide Data

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Trying to plan a maritime operation usually means bouncing between three different websites and spreadsheets.

The QWeather Ocean/Tide API MCP Server: Getting precise tide metrics in seconds.

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

Planning a deep-sea survey route

Auditing port expansion logistics

Investigating historical flooding patterns

Emergency response coordination

The honest tradeoffs

Assuming general weather data is enough

Ignoring service status checks

Using general coordinates incorrectly

When It Fits, When It Doesn't

Questions you might have