Ferryhopper Mcp Server

Created By
FerryhopperOrg8 months ago
Ferry trip planning powered by live data from Ferryhopper — integrate into your AI assistant for fast, reliable ferry search and booking redirects.
Overview

what is Ferryhopper MCP Server?

Ferryhopper MCP Server is a ferry trip planning tool that utilizes live data from Ferryhopper to facilitate fast and reliable ferry searches and booking redirects.

how to use Ferryhopper MCP Server?

Integrate the Ferryhopper MCP Server into your AI assistant by configuring it with the provided server command and parameters. Users can then query ferry routes and schedules through the assistant.

key features of Ferryhopper MCP Server?

  • 🌍 Search ports and connections across 33 countries and 190+ ferry operators
  • ⛴️ Get real-time ferry itineraries with indicative prices
  • 🔗 Receive a direct link to Ferryhopper.com for booking and payment

use cases of Ferryhopper MCP Server?

  1. Assist users in searching for ferry routes and daily itineraries.
  2. Recommend destinations based on departure port and date.
  3. Power travel chatbots to plan island-hopping or multi-leg journeys.

FAQ from Ferryhopper MCP Server?

  • Can I use this server for all ferry routes in Europe?

Yes! The server covers a wide range of ferry routes across Europe and the Mediterranean.

  • Is there a cost associated with using the Ferryhopper MCP Server?

The server is free to use for integration into your applications.

  • How do I configure the server?

Follow the installation instructions provided in the documentation to set up the server in your AI assistant.

Server Config

{
  "mcpServers": {
    "ferryhopper-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.ferryhopper.com/mcp"
      ]
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
FerryhopperOrg
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago