Timetable API Node vs Vesselapi MCP

In-depth architectural comparison of the Timetable API Node and Vesselapi MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Timetable API Node when:

• You need dedicated capabilities in the Travel & Transportation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: SENTRY_DSN, NEW_RELIC_LICENSE_KEY.
• Primary tools included: Real-time stop arrival predictions, Live vehicle position tracking, Route geometry and static data from GTFS.

Explore Timetable API Node Details

Choose Vesselapi MCP when:

• You need dedicated capabilities in the Travel & Transportation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: VESSELAPI_API_KEY.

Feature & Specification Comparison

Specification	Timetable API Node vbhjckfd Travel & Transportation	Vesselapi MCP vessel-api Travel & Transportation
Summary	Real-time Lviv (Ukraine) public transport: stop arrivals, live vehicle positions, route geometry, and nearby stop discovery. No API key required.	Maritime vessel tracking via VesselAPI. Search vessels, get real-time positions, ETAs, port events, emissions, inspections, and NAVTEX safety messages.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "vbhjckfd-timetable-api-node": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ],
      "env": {
        "SENTRY_DSN": "YOUR_SENTRY_DSN_HERE",
        "NEW_RELIC_LICENSE_KEY": "YOUR_NEW_RELIC_LICENSE_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "vessel-api-vesselapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ],
      "env": {
        "VESSELAPI_API_KEY": "YOUR_VESSELAPI_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons