SkyAccess

SkyAccess MCP server

[MCP Badge]

SkyAccess is the world's largest empty leg marketplace by listing volume. This free, public MCP server lets any AI assistant search 5,000+ live empty leg flights from 900+ FAA Part 135 (and international equivalent) certified charter operators, often 25 to 75% below a comparable full charter. It also returns indicative charter price estimates and a booking link the traveler can open.

Use the hosted endpoint. Nothing needs to be installed.

https://mcp.skyaccess.com/mcp

Install

Each option below adds the hosted endpoint to your client. Nothing runs on your machine, and there is no account, sign-up or API key.

[Install in VS Code] [Install in VS Code Insiders]

• Claude Code:

  bash

  claude mcp add --transport http skyaccess https://mcp.skyaccess.com/mcp

• Claude Code plugin (the same server, plus a skill that tells Claude when to use each tool):

  bash

  claude plugin marketplace add sky-access/skyaccess-mcpclaude plugin install skyaccess@skyaccess

• Gemini CLI:

  bash

  gemini extensions install https://github.com/sky-access/skyaccess-mcp

• VS Code (GitHub Copilot): use a button above, or run:

  bash

  code --add-mcp '{"name":"skyaccess","type":"http","url":"https://mcp.skyaccess.com/mcp"}'

• Claude (claude.ai and Claude Desktop), Cursor and other clients: see Connect from an MCP client.

Other clients

This repository also ships a package for each client below. Each one points at the same hosted endpoint and runs nothing on your machine.

Kiro

In the Powers panel choose Add Custom Power, then Import power from GitHub, and enter https://github.com/sky-access/skyaccess-mcp. The power in powers/skyaccess adds the server and a skill that tells the Kiro agent when to use each tool.

Gemini CLI

gemini extensions install https://github.com/sky-access/skyaccess-mcp

The extension is defined in gemini-extension.json and GEMINI.md.

Google Antigravity

Add the server to ~/.gemini/config/mcp_config.json, or to .agents/mcp_config.json in a workspace. Antigravity reads serverUrl, not url:

{ "mcpServers": { "skyaccess": { "serverUrl": "https://mcp.skyaccess.com/mcp" } } }

Or install the plugin folder from a clone of this repository with /plugin install <path-to-clone>/integrations/antigravity/skyaccess. See integrations/antigravity/skyaccess.

GitHub Copilot CLI

copilot plugin marketplace add sky-access/skyaccess-mcpcopilot plugin install skyaccess@skyaccess

This installs plugins/skyaccess, which carries an Agent Plugins plugin.json and mcp.json for Copilot next to the Claude Code manifests.

Connection details

Connect from an MCP client

Any client that supports remote MCP servers over Streamable HTTP can use the endpoint directly. Leave authentication empty.

• Claude (claude.ai and Claude Desktop): Settings, Connectors, Add custom connector, then paste https://mcp.skyaccess.com/mcp.

• Claude Code, Gemini CLI and VS Code: see Install.

• Cursor: add this to ~/.cursor/mcp.json:

  json

  { "mcpServers": { "skyaccess": { "url": "https://mcp.skyaccess.com/mcp" } } }

• VS Code, by hand: add this to .vscode/mcp.json in your workspace:

  json

  { "servers": { "skyaccess": { "type": "http", "url": "https://mcp.skyaccess.com/mcp" } } }

• Clients that only speak stdio (for example Claude Desktop's claude_desktop_config.json file): use the bridge in this repository. See Local installer and stdio bridge.

Try it with curl

List the tools:

curl -sS https://mcp.skyaccess.com/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Search empty legs (read-only):

curl -sS https://mcp.skyaccess.com/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_empty_legs","arguments":{"origin":"Los Angeles","destination":"Las Vegas","passengers":4}}}'

The server is stateless, so both commands work without an initialize handshake. MCP clients still send one, and the server answers it normally.

Tools

A flight with price: null has no published price (SkyAccess shows it as "Contact for price"). Such flights can appear even when max_price is set, because their price is unknown.

Every tool carries MCP annotations: the four read-only tools set readOnlyHint: true, and request_booking sets readOnlyHint: false.

Example prompts

1. "Find me a private jet from Los Angeles to Las Vegas this week for 4 people." (search_empty_legs)
2. "Are there any cheap private jet flights from Miami to the Bahamas?" (search_empty_legs)
3. "Show me empty legs from Teterboro to Palm Beach and give me the booking link for the cheapest one." (search_empty_legs, then booking_handoff)
4. "How much would it cost to charter a private jet from Teterboro to Aspen for 6 people?" (get_charter_estimate)
5. "What private jet deals are leaving Dallas this weekend?" (search_empty_legs)
6. "Roughly what does a private jet from New York to London cost for 8 passengers?" (get_charter_estimate)

Inventory changes all the time, so the flights returned differ from run to run.

Data and privacy

The four read-only tools need no personal data. request_booking is the only tool that sends personal data: the name and email the traveler gives, plus the trip details and any notes, go to SkyAccess so a specialist can reply. Call it only when the traveler asks SkyAccess to contact them.

How SkyAccess handles this data: https://skyaccess.com/privacy#connector

Rate limits

Current limits, per client IP:

• Tool calls: 30 requests per 60 seconds. Each request that carries a tools/call counts once. Connection setup is not counted: initialize, notifications/initialized, notifications/cancelled, tools/list, ping, and the GET an MCP client sends to open the optional SSE stream (answered 405). A typical client turn (connect, list tools, call one tool) therefore spends 1 request. Any other method counts, and so does a setup request that is over 8 KB, chunked or compressed, or a batch that repeats a setup method. Counted tool-call responses carry RateLimit-Policy: 30;w=60, RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers (a request_booking response carries the hourly limit's values instead); setup responses carry none.
• 10 charter enquiries per hour. Only requests that call request_booking count toward this limit.
• Per request: a JSON-RPC batch may carry at most 4 tool calls, and at most 1 request_booking call. Larger batches return 400.

Over a limit, the server answers HTTP 429 with JSON-RPC error code -32029. The RateLimit-Reset header gives the seconds until the window resets; retry after that.

Troubleshooting

Local installer and stdio bridge (npm package)

The skyaccess-mcp npm package does two things. It needs Node 20 or later and has no runtime dependencies.

1. It writes the SkyAccess entry into the config of supported MCP clients found on the machine (Cursor and the Claude Desktop config file), so nobody has to hand-edit JSON.
2. It provides a stdio to HTTP bridge for clients that cannot take a URL.

npx -y skyaccess-mcp              # register with every supported client found on this machinenpx -y skyaccess-mcp --dry-run    # show what would be written, write nothingnpx -y skyaccess-mcp doctor       # check the endpoint and list its toolsnpx -y skyaccess-mcp bridge       # the stdio to HTTP bridge (clients spawn this)

doctor checks the endpoint and lists its tools. It exits non-zero if the endpoint is unreachable or returns no tools.

To use the bridge by hand with a stdio-only client such as Claude Desktop's claude_desktop_config.json:

{  "mcpServers": {    "skyaccess": {      "command": "npx",      "args": ["-y", "skyaccess-mcp", "bridge"]    }  }}

The same commands work from a clone of this repository with node bin/skyaccess-mcp.mjs <command>.

Options: --url <url>, --client <cursor|claude-desktop>, --dry-run, --help.

How the installer treats your config files

• It only writes to a client whose own directory already exists, so it never creates ~/.cursor on a machine without Cursor.
• It keeps every other key in the file, so your other MCP servers stay as they are.
• It leaves a config that does not parse as JSON untouched and reports it; it never overwrites one.
• It backs up an existing SkyAccess entry to <config>.skyaccess-backup before replacing it.

Design notes

• No runtime dependencies, so there is no transitive supply chain to audit. Plain ESM with no build step: what ships is what is in src/.
• The bridge writes only JSON-RPC to stdout, one message per line, and sends every diagnostic to stderr. A stray stdout write would corrupt the protocol.
• A notification answered with 202 produces no stdout line, because a reply the client never asked for is a protocol violation.
• A failed HTTP hop for a request becomes a JSON-RPC error with the same id, so the client fails fast instead of waiting forever.

Development

npm install          # installs vitest, the only dev dependencynpm test             # offline suite against a real local HTTP server, no networknpm run test:live    # opt-in live suite against https://mcp.skyaccess.com/mcp

The live suite only sends initialize and tools/list. It is kept out of npm test because it depends on DNS and the public internet, neither of which says anything about whether the code is correct.

Listing manifests

These files point each client at the hosted endpoint. None of them runs code.

When the server version changes, bump version in gemini-extension.json, plugins/skyaccess/.claude-plugin/plugin.json, plugins/skyaccess/plugin.json and powers/skyaccess/plugin.json together. The Antigravity manifest has no version field. The Dify plugin has its own version in integrations/dify/manifest.yaml. Check the Claude Code files with claude plugin validate . and claude plugin validate ./plugins/skyaccess, and the Gemini extension with gemini extensions validate ..

License

MIT. See LICENSE.