A side-by-side look at the Ocean Schedules and Freight Pulse MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ocean Schedules for travel & transportation work; choose Freight Pulse for travel & transportation as a local process. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 32/100 · Emerging | 39/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Ocean Schedules | View Freight Pulse |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
No confirmed install command for Ocean Schedules yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"freight-pulse": {
"command": "npx",
"args": [
"-y",
"freight-pulse-mcp"
]
}
}
}