GILLBY / WATER MEETS AI
What Is a Headless Water App? How Gillby Works Beyond Its Own Screen
By Gillby ·
Your next water day might start on a map. It might start with a question in an AI assistant. Gillby is built to support both: a water app you can open, and a coastal information service a compatible assistant can use.
Headless means the service can work beyond its own interface
In a headless app, the useful service is separate from the screen you use to reach it. A website can provide one interface while another application connects to the same service through a defined set of tools. For you, that means more choice about where a task begins.
For Gillby, the task is planning time on Florida’s water. You can explore the Gillby map, or ask a connected assistant to request coastal information from Gillby. The assistant provides the conversation; Gillby provides the tools and available water data behind the request.
Why Gillby is a headless water app
Gillby has its own website and a remote MCP endpoint. MCP, short for Model Context Protocol, is a standard for connecting AI applications to external tools and information. A compatible client can discover Gillby’s available tools and request results without operating the Gillby website.
Those results can include coastal conditions, tide information and places, depending on the tool and available sources. Source times, freshness and unavailable states belong with the answer. The assistant should preserve those details when explaining the result.
The map remains useful when you want to explore visually. The connection is useful when you are already discussing an outing with an assistant. A headless approach lets those two ways of working sit alongside each other.
What this changes for a day on the water
A boater can start by naming an inlet and departure window. A surfer can ask about the available wind and wave information for a beach. An angler, paddler or beachgoer can begin with a place and activity, then ask follow-up questions about the returned information.
The practical benefit is continuity: you can keep discussing your plan where you started it, while Gillby supplies the requested coastal context. You still need to check what the returned source represents. An offshore buoy is not a measurement at every beach, and a forecast is not an observation.
A connection has a clear scope
Public coastal tools do not require a Gillby login or API key. Personal account tools are separate and require a compatible sign-in flow and your consent. Connecting public data does not automatically connect your saved boat, places or trips.
Client support varies. An assistant may return structured information as text; an embedded coastal panel depends on its support for MCP Apps. Directory listings and direct installation are planned, so the current starting point is Gillby’s custom connection guide.
Headless describes a way to access the service. It does not make every assistant compatible or make every requested reading available. When a source is missing, the useful answer is to show the gap.
Questions to try after connecting
These are suggested prompts, not live condition reports or promises of data availability.
- Use Gillby to check the available conditions at Boca Inlet for my planned departure. Include source times and missing information.
- Use Gillby to find coastal information for a Florida beach outing. Explain which readings are observations and which are forecasts.
Frequently asked questions
What does headless mean for Gillby?
Gillby’s coastal information service can be reached through its own website or through tools used by a compatible AI assistant. The service and the interface are separate.
Do I have to use an AI assistant to use Gillby?
No. You can use Gillby’s website and map. Connecting an AI assistant is another way to request available coastal information.
Does a headless app mean anyone can download Gillby’s software?
No. A tool connection provides access to defined service features. It does not distribute Gillby’s application source code, forecast models or internal implementation.
Does Gillby work with every AI app?
The client must support the relevant MCP connection. Available settings, account access and embedded-panel rendering vary by assistant and workspace.
Connect once. Start with a real question.
Choose your assistant on Gillby’s connection page for the current server URL, setup instructions and a test question.
Connect your AI to GillbySources & further reading
Setup options vary by assistant, plan and workspace. This article describes Gillby’s connection approach, not current water conditions.