BEACON MCP

BEACON is an official MCP server by Virtual Hangar that connects AI assistants to private aircraft data. It allows users to look up FAA records, estimate charter costs, check availability, and send trip or buyer inquiries to aircraft owners who have opted in. The server operates without authentication and respects owner privacy settings.

Endpoint and access

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

No sign-inEndpoint checked 2026-10-18Operated by Virtual Hangar Media, LLC

MCP endpoint (Streamable HTTP)

https://owners.virtualhangar.com/mcp/beacon

Vendor documentation

What you can do with it

Look up aircraft FAA records and owner-published facts
Estimate approximate charter costs for specific routes
Check aircraft availability for specific dates
Send trip requests or buyer inquiries to owners

Tools advertised by the last live check:

get_aircraft
search_aircraft
estimate_charter
check_availability
request_trip
send_buyer_inquiry

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 beacon-mcp https://owners.virtualhangar.com/mcp/beacon

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 beacon-mcp --url https://owners.virtualhangar.com/mcp/beacon

Cursor

Merge this server into .cursor/mcp.json in your project, then enable beacon-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "beacon-mcp": {
      "url": "https://owners.virtualhangar.com/mcp/beacon"
    }
  }
}

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": {
    "beacon-mcp": {
      "type": "streamableHttp",
      "url": "https://owners.virtualhangar.com/mcp/beacon",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start beacon-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "beacon-mcp": {
      "type": "http",
      "url": "https://owners.virtualhangar.com/mcp/beacon"
    }
  }
}

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 beacon-mcp https://owners.virtualhangar.com/mcp/beacon

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": {
    "beacon-mcp": {
      "url": "https://owners.virtualhangar.com/mcp/beacon"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "beacon-mcp": {
      "serverUrl": "https://owners.virtualhangar.com/mcp/beacon"
    }
  }
}

See all 2,337

Do you run BEACON MCP?

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