Ferryhopper Mcp Server

Created By
Ferryhopper8 months ago
Ferryhopper MCP Server - Ferry trip planning through ferryhopper.com Ferryhopper MCP Server connects your AI assistant with Ferryhopper’s extensive ferry network, making ferry travel planning seamless and smart. Whether you’re looking for a single route or an island-hopping adventure, your assistant can tap into live ferry data from across Europe and the Mediterranean. Key Features 🌍 Search ports and connections across 33 countries and 190+ ferry operators ⛴️ Get real-time ferry itineraries with indicative prices to plan ahead with confidence 🔗 Receive a direct link to Ferryhopper.com to continue your search and complete bookings effortlessly Use Cases 🔹 Assist users in searching for ferry routes and finding daily itineraries 🔹 Enable AI assistants to recommend destinations based on a departure port and date 🔹 Build travel chatbots that provide ferry planning guidance and suggest optimal journeys With Ferryhopper MCP Server, your AI assistant becomes a reliable travel companion — helping users discover the best routes, compare options, and plan their journeys with ease. Available tools Get ports { "name": "get_ports", "description": "Get a list of global ports and their details" } } Search Trips { "name": "search_trips", "description": "Get a list available ferry trips between two ports on a specific date", "parameters": { "departurePort": "string", "arrivalPort": "string", "date": "string (YYYY-MM-DD)" } } } Redirect to Ferryhopper { "name": "redirect_to_search_results_page", "description": "This tool returns a redirection URL to the search results page for the user to proceed to the booking flow", "parameters": { "departurePort": "string", "arrivalPort": "string", "ownerCompany": "string", "departureDateTime": "string", "arrivalDateTime": "string", "vesselID": "string" } } } Claude Desktop Installation Guide Adding a Custom Connector in Claude Teams Note: Only workspace admins or owners can complete these steps. Open Settings in Claude Teams. Select Connectors, then switch to the Organization connectors tab at the top. Scroll to the bottom and choose Add custom connector. Provide the following details: Name: ferryhopper-mcp-server Remote MCP server URL: https://mcp.ferryhopper.com/mcp Click Add to finalize the connector setup. Configuring Claude Desktop 1. Verify Node.js is Installed Open a terminal and run: node -v If no version number appears, install Node.js from nodejs.org.\ 2. Update the Claude Desktop Configuration In Claude Desktop, open Settings and go to Developer. Click Edit config to open claude_desktop_config.json. Insert the MCP server details into the mcpServers section. Save your changes and restart Claude Desktop. ✅ After restarting, Claude Desktop will connect to the Ferryhopper MCP server. Configuration: { "mcpServers": { "ferryhopper-mcp-server": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://mcp.ferryhopper.com/mcp"] } } } Example Prompts Simply ask your AI assistant something like: “What ferries depart from Piraeus to Aegina on Saturday morning?” “Help me find a ferry from Ibiza to Barcelona on July 11th for 2 adults and 1 child (7 years old).” “I want to visit an island within 3 hours of Athens tomorrow and return the next day — what are my options?”

Server Config

{
  "mcpServers": {
    "Sentry": {
      "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
Ferryhopper
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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