BeachFinder MCP Server

BeachFinder MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Search 184,900 swim spots, conditions, water activities, providers and guides worldwide.

What you get

BeachFinder gives AI assistants read-only access to public discovery across 184,900 beaches, lakes and swimming spots worldwide. It can rank places for a user's real intent, compare options, add current planning signals where coverage exists, and always return a canonical BeachFinder link.

• Find beaches, lakes, bathing places and natural swimming spots by destination or consented location
• Compare water and air temperature, wind, gusts, UV, waves and currents where available
• Search for surf, diving, snorkeling, river, whitewater and vanlife-relevant locations
• Discover source-backed water-activity providers without exposing private or direct contact data
• Find practical destination, GTA 6 and football travel guides
• Read anonymous community-condition summaries without user identities

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once BeachFinder is connected, these are the calls the assistant has available:

• Field — Value
• Transport — Streamable HTTP, stateless
• Authentication — None for public read-only tools
• OpenAPI — https://getbeachfinder.com/openapi.json
• Version — 1.0.1

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the beachfinder mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. BeachFinder's toolset — Field, Transport, Authentication and 2 more — is a fair guide to whether it matches your workflow. It is maintained by com.getbeachfinder; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.