Skip to content
Developer docs: all pages

AI assistants (MCP)

The Voydar MCP server lets AI assistants (Claude, ChatGPT, Cursor, VS Code and any other MCP client) look up vessels, tracks, ports, companies and sanctions for you, and follow the ships and ports you care about. It is hosted: there is nothing to install.

Server address (Streamable HTTP):

https://www.voydar.com/mcp

Sign in with OAuth: assistants that support it (Claude, ChatGPT, Cursor, VS Code, the MCP inspector) send you to Voydar to approve the connection, and it then uses your account's API allowance. Or connect with your Voydar API key in the Authorization header, exactly as for the REST API; the free Sandbox key works. Connecting and listing tools are free. Each data tool call is one API request with the same credits, rate limit and rights: withheld fields stay withheld, and every result carries the attribution to show and your plan's commercial-use scope. Connected apps are listed, and can be disconnected, under Account, API keys.

Tools (read-only, except follow_entity and unfollow_entity, which change only your own follows):

  • search_entities
  • get_vessel
  • get_vessel_track
  • get_vessel_status
  • get_port
  • get_port_calls
  • get_company
  • list_sanctioned_vessels
  • screen_vessels
  • get_chokepoint_transits
  • get_usage
  • get_my_feed
  • search
  • fetch
  • follow_entity
  • unfollow_entity
  • list_my_follows
  • list_my_recent_alerts
  • list_data_sources
  • get_trade_flows
  • get_commodity
  • get_freight_rate

It also offers a resource explaining data rights and attribution (voydar://docs/rights) and two prompts: a vessel due-diligence brief and a port activity brief.

Trade, commodity and freight data, on every plan including the free Sandbox: list_data_sources (free) shows which datasets exist, their licence, newest period, last load and whether each is served; get_trade_flows, get_commodity and get_freight_rate cost 1 credit each. These are reported government statistics with the source and licence of each series, not a voyage model. Sources that are not licensed for API use, or that Voydar holds pending a rights decision, are listed as withheld with the reason and are never served. No commodity price series is loaded (get_commodity returns price: null), and some registered datasets have not been loaded yet, so check list_data_sources first. The same data is at /api/v1/trade/*, and two more prompts cover a commodity briefing and a freight market snapshot. A server-side release switch applies: while it is off for your account, these tools are not listed and the endpoints answer 404.

One-click install

These buttons connect with OAuth: your client opens a Voydar sign-in, no key needed. A free account works, and following a ship starts a free 14-day Plus trial, no card.

Opens Voydar in Claude's Connectors Directory: choose Connect and approve on Voydar. You can also add it as a custom connector with the URL above.

Claude Code plugin

The Voydar plugin adds the server plus skills for vessel tracking, port briefings, company fleets and sanctions checks:

claude plugin marketplace add CommonElements/tsg-claude-plugins
claude plugin install voydar@tsg-plugins

Listed in the official MCP Registry as com.voydar/voydar.

Add Voydar to your assistant

  • Claude.ai and the Claude apps: Voydar is in Claude's Connectors Directory (https://claude.ai/directory/voydar). Choose Connect, and Claude sends you to Voydar to approve. A connector added on claude.ai also appears in the Claude desktop and mobile apps. Adding it as a custom connector with the server address also works.
  • Claude Desktop: the same Settings, Connectors, Add custom connector (no config file needed). The config-file bridge below is only for connecting with an API key.
  • ChatGPT: in Settings, Apps and Connectors, Advanced settings, turn on developer mode; then create a connector with the server address and OAuth authentication, and approve on Voydar. Turn it on in a chat from the tools menu.
  • ChatGPT deep research and other search-style connectors use the search and fetch tools: search returns ids, titles and Voydar page links, and fetch returns the full record for an id.
Claude Code (terminal), signing in with your Voydar account:
claude mcp add --transport http voydar https://www.voydar.com/mcp
# then, inside Claude Code: /mcp, choose voydar, Authenticate
Cursor (~/.cursor/mcp.json; Cursor opens the Voydar sign-in):
{
  "mcpServers": {
    "voydar": { "url": "https://www.voydar.com/mcp" }
  }
}
VS Code (.vscode/mcp.json; VS Code opens the Voydar sign-in):
{
  "servers": {
    "voydar": { "type": "http", "url": "https://www.voydar.com/mcp" }
  }
}
Claude Code with an API key instead:
claude mcp add --transport http voydar https://www.voydar.com/mcp \
  --header "Authorization: Bearer $VOYDAR_API_KEY"
Claude Desktop with an API key (claude_desktop_config.json, through the mcp-remote bridge):
{
  "mcpServers": {
    "voydar": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.voydar.com/mcp", "--header", "Authorization:${VOYDAR_AUTH}"],
      "env": { "VOYDAR_AUTH": "Bearer sk_sdr_…" }
    }
  }
}
OpenAI API (Responses API): add Voydar as a remote MCP tool with your key:
curl https://api.openai.com/v1/responses \
  -H "Authorization: Bearer $OPENAI_API_KEY" -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5",
    "tools": [{
      "type": "mcp",
      "server_label": "voydar",
      "server_url": "https://www.voydar.com/mcp",
      "headers": { "Authorization": "Bearer '"$VOYDAR_API_KEY"'" },
      "require_approval": "never"
    }],
    "input": "Is the vessel IMO 9811000 on any sanctions list?"
  }'

To connect Cursor or VS Code with a key instead of signing in, add "headers": { "Authorization": "Bearer sk_sdr_…" } next to "url". A key in a config file is a secret: do not commit it or share the file.

What each plan gets over MCP

A connection uses the allowance of the account that approved it, the same as that account's API keys. Looking things up works on every plan, Free included; paid plans add volume, history and commercial use.

PlanCredits a monthRequests per secondTrack historyFollowsCommercial use
Free2,500230 days5No, personal use
Plus5,0002365 days50No, personal use
Pro25,0005Full archive500Internal business use
Developer25,000530 daysAs your membershipYour business and your own product
Growth250,00020730 daysAs your membershipYour business and your own product
Scale2,500,00050Full archiveAs your membershipYour business and your own product

Team and Enterprise seats get the Pro allowance. An API plan and a membership never add up: the larger allowance applies. When a limit is reached, the assistant is told which limit it was and where to compare plans.

Compare plans