Koskamo

SchedulesMCP MCP server

SchedulesMCP is an official MCP server by Navo24 that allows AI agents to compare ocean carrier schedules, transit times, and on-time reliability across 60+ carriers. It provides tools to find upcoming sailings, rank them by reliability, compare lanes, and check port congestion, enabling data-driven pre-booking decisions for freight forwarding.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Navo24
MCP endpoint (Streamable HTTP)
https://mcp.schedulesmcp.com/mcp
Vendor documentation

What you can do with it

  • Find upcoming sailings on a specific lane
  • Rank sailings by reliability and transit time
  • Compare on-time records for carriers on a lane
  • Check port congestion and dwell times
Tools advertised by the last live check:
  • compare_lanes
  • carrier_reliability
  • transit_time
  • find_sailings
  • get_schedules
  • find_best_sailings
  • watch_lane
  • port_reliability
  • carrier_league
  • port_congestion
  • active_cyclones
  • lane_storm_exposure

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http schedulesmcp https://mcp.schedulesmcp.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add schedulesmcp --url https://mcp.schedulesmcp.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable schedulesmcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "schedulesmcp": {
      "url": "https://mcp.schedulesmcp.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "schedulesmcp": {
      "type": "streamableHttp",
      "url": "https://mcp.schedulesmcp.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start schedulesmcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "schedulesmcp": {
      "type": "http",
      "url": "https://mcp.schedulesmcp.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http schedulesmcp https://mcp.schedulesmcp.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "schedulesmcp": {
      "url": "https://mcp.schedulesmcp.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "schedulesmcp": {
      "serverUrl": "https://mcp.schedulesmcp.com/mcp"
    }
  }
}

Do you run SchedulesMCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing