Skip to content

Connect your assistant

For Cursor, Claude, and Grok inside Cursor, add only this URL:

https://api.flyga.app/mcp

Keep /mcp. Do not add a trailing slash. Do not add headers.

FieldValue
Server URLhttps://api.flyga.app/mcp
AuthOAuth — the client opens Flyga’s login page
TransportStreamable HTTP (some clients label this HTTP or Remote)

Look for MCP, Connectors, or Apps. After you save, quit and reopen a desktop app if the new server does not appear. Disconnect later from go.flyga.app Account → Connected apps. Usage on that row is the recent MCP tool calls from the connection — the same kind of history as an API key.

When the browser opens, sign in on Flyga (email code or passkey), then click Allow.

Add this under Cursor Settings → MCP, or in ~/.cursor/mcp.json:

{
"mcpServers": {
"flyga": {
"url": "https://api.flyga.app/mcp"
}
}
}

Cursor opens Flyga’s login page on go.flyga.app. Sign in, click Allow, and the green connected state should appear. Grok inside Cursor uses that same connection.

On claude.ai or Claude Desktop:

  1. Open Customize → Connectors.
  2. Click Add custom connector.
  3. Name it Flyga. URL: https://api.flyga.app/mcp.
  4. Save, then in a chat use + → Connectors and turn Flyga on. Sign in on Flyga when the browser opens, then click Allow.

Claude Code:

Terminal window
claude mcp add --transport http flyga https://api.flyga.app/mcp

Ask:

What should I do with these points?

Flyga reads your wallet, then ranks which points to transfer from what you hold. More prompts: What to ask.

Scheduled jobs, cron, and raw HTTP use an MCP key instead of a browser login. Mint one in Create an MCP key.

Send all three:

  • Authorization: Bearer plus the flyga_mcp_ secret
  • Accept: application/json, text/event-stream
  • a Chrome User-Agent

Keep the secret in the job’s environment or the client’s private config — not in a chat message.