MCP Integration

FlyPix's API is also available as an MCP (Model Context Protocol) server, so AI assistants such as Claude can work with your FlyPix data directly: listing projects, reading rasters and vectors, applying models, and anything else the API offers.

The server is reachable at:

https://api.flypix.ai/mcp

It uses the Streamable HTTP transport.

What it exposes

The MCP server offers one tool per operation of the API, generated from the same specification. The tools therefore always match the REST API: when an endpoint is added or changed, its tool follows automatically, with the same parameters and responses.

Every tool call behaves exactly like the equivalent REST request. It is subject to the same permissions and subscription limits, and returns the same errors.

note

Endpoints that upload files or return binary content are not available as tools. Use the REST API or the SDK for those.

Authentication

The MCP server accepts the same API key as the REST API, passed in an ApiKey header on every request. See Authentication for how to create one.

An assistant acts with your permissions

An API key carries your full permissions in the tenant it was created in. An assistant connected with that key can do anything you can, including editing and deleting data. Review the actions your assistant proposes before approving them.

Connecting Claude Code

Claude Code supports remote MCP servers with custom headers directly:

claude mcp add --transport http flypix https://api.flypix.ai/mcp \
  --header "ApiKey: <YOUR_API_KEY_HERE>"

Connecting Claude Desktop

Claude Desktop, like most MCP clients, cannot yet send a fixed header to a remote server. Bridge the connection with mcp-remote, which runs locally and adds the header for you. This requires Node.js to be installed.

Add the server to Claude Desktop's claude_desktop_config.json, found at:

System	Location
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Windows	%APPDATA%\Claude\claude_desktop_config.json
Linux	~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "flypix": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.flypix.ai/mcp",
        "--header",
        "ApiKey:${FLYPIX_API_KEY}"
      ],
      "env": {
        "FLYPIX_API_KEY": "<YOUR_API_KEY_HERE>"
      }
    }
  }
}

A few details to keep in mind:

• Write the --header value without spaces around the :. This is the syntax mcp-remote expects.
• Fully quit and relaunch Claude Desktop after editing the file. It only reads its configuration at startup.

The same mcp-remote setup works for other MCP clients that only support local servers; refer to their documentation for where the configuration goes.

Troubleshooting

If a tool call fails or behaves unexpectedly in Claude Desktop, its log file mcp-server-flypix.log contains the raw traffic between Claude and the server. It is located in Claude's log directory:

System	Location
macOS	~/Library/Logs/Claude/
Windows	%APPDATA%\Claude\logs\
Linux	~/.config/Claude/logs/

Authentication errors usually mean the key has expired, was deleted, or is being used for a different tenant than the one it was created in.