Gillby / AI connections

Your water guide.
In your favorite AI.

Ask about conditions, find coastal places and plan your day using Gillby’s data inside your assistant. Choose your assistant below to get started.

Public conditions need no Gillby login or API key.

Browse every MCP tool, inputs & permissions →Build with the HTTP API →

Step 1 / Choose your assistant

Gillby, where you already ask.

Bring marine conditions, tides and coastal places into your AI assistant. MCP is the connection that lets your assistant ask Gillby for data.

Connect ChatGPT

Open Plugins in ChatGPT. Choose Add, then Add custom MCP server. Some accounts call this Apps or Connectors; your workspace may require admin access.
Enter Gillby as the name and paste the server URL below. For public conditions, choose No authentication. Review the notice, create the plugin, then select Connect.
Start a new chat and select Gillby from your available plugins or tools. Paste the test question below.

Open ChatGPT Official setup guide

Asked for an icon? Download Gillby’s icon (PNG, 256 × 256, under 10 KB).

Step 2 / Copy your connection details

One URL. No API key for public data.

Loading this instance’s connection details…

Connection type: Streamable HTTP
Public data authentication: None / No sign-in

Connecting a saved boat or personal account?

Public access does not sign in to your Gillby account. Personal tools require OAuth and an explicit Gillby consent screen. Select OAuth or optional sign-in in a compatible client and review the requested account permissions. Account tools can manage saved data after authorization; approve changes deliberately.

Manage or revoke Gillby account permissions

Also disconnect the connector in your assistant to remove its public tool access.

Step 3 / Try your first question

Check the connection in a new chat.

Test question

Use Gillby to check current conditions at Boca Inlet. Show the coastal panel if supported, and include source freshness and any unavailable data.

Tools are working when…

Your assistant calls Gillby and returns sourced conditions or an explicit source-unavailable result. A general answer without a Gillby tool call does not verify the connection.

The embedded UI is working when…

An interactive coastal panel appears inside the conversation. Tool access and panel rendering are separate checks. Rendering in consumer Claude and ChatGPT has not yet been verified by Gillby.

This page cannot inspect your assistant’s connection. Copying a URL or opening an assistant does not connect it automatically.

Need a hand?

I can’t find Add custom MCP server

Your assistant’s menu names and access depend on the account and workspace. Look under Plugins, Apps or Connectors. Ask your workspace admin if custom servers are restricted, or follow the official guide above.

The server won’t connect

Use the full HTTPS URL ending in /mcp, with no extra spaces. Select Streamable HTTP where offered. For public conditions choose no authentication. A local HTTP address cannot be reached by a cloud assistant.

It is connected, but Gillby isn’t answering

Start a new chat, enable Gillby in that chat’s tools, and explicitly ask to use Gillby. Approve tool access if prompted. Refresh tools in the connector settings if the catalog is out of date.

I see text, but no interactive panel

Ask for current conditions and the coastal panel. Gillby’s get_conditions and get_point_conditions tools provide panel metadata. The assistant must support MCP Apps and render that resource; other clients can still return tool results as text.

My saved boat or trips aren’t available

A public connector has no Gillby account session. Reconfigure it for OAuth or optional sign-in where supported, sign in to the correct Gillby account, and review consent. Never paste your password or a private API key into a chat.

How do I disconnect?

Remove or disconnect Gillby in your assistant’s settings. If you signed in to Gillby through OAuth, also revoke the account permission using the link above.

Developer details and API

The remote endpoint uses Streamable HTTP. Clients that implement MCP Apps can request Gillby’s coastal panel; other clients receive structured tool results. Personal account tools require OAuth consent.

A separate stdio adapter is available in a Gillby checkout at scripts/mcp/server.ts. It runs with npm run mcp and reads the API base URL from TROSI_API_URL. This adapter exposes tools, without the remote server’s embedded panel.

View the OpenAPI schema