Connect via MCP

Use Fload from Claude, Cursor, ChatGPT or any MCP client. Ask about installs, reviews and ad spend, draft replies, propose listing changes and set up your agents, all from the AI app you already use. Anything that changes your app still waits for your approval.

What you get

Connect in three steps

Every AI app connects to the same server: https://api.fload.com/mcp. There's no key to paste. The first time your AI app uses Fload, a browser opens so you can sign in, pick an organization and click Allow.

claude mcp add --transport http --scope user fload https://api.fload.com/mcp

Set up your AI app

Claude Code

1. In your terminal, run:

claude mcp add --transport http --scope user fload https://api.fload.com/mcp

2. Start Claude Code and type /mcp. Pick fload, choose Authenticate, then sign in to Fload in the browser and click Allow.
3. Ask something like "Which of my apps lost downloads this week?"

--scope user makes Fload available in every project. Leave it out to add Fload to the current project only.

With an API key instead of signing in, for scripts and CI:

claude mcp add --transport http --scope user fload https://api.fload.com/mcp \
  --header "Authorization: Bearer fload_sk_your_key_here"

With the local npm package:

claude mcp add --env FLOAD_API_KEY=fload_sk_your_key_here --transport stdio \
  --scope user fload -- npx -y @fload-ai/mcp

Claude (desktop app and claude.ai)

1. In Claude, open Settings › Connectors and click Add custom connector.
2. Name it Fload and paste https://api.fload.com/mcp as the URL. Click Add.
3. Click Connect, sign in to Fload and click Allow.

On Team and Enterprise plans, an owner adds the connector once under Organization settings › Connectors, and each member then clicks Connect. The Free plan allows one custom connector. A connector you add in Claude also shows up in Claude Code.

Prefer a config file? Claude Desktop's config file runs local servers, so use the npm package with an API key. Add this to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows, then quit Claude completely and open it again:

{
  "mcpServers": {
    "fload": {
      "command": "npx",
      "args": ["-y", "@fload-ai/mcp"],
      "env": { "FLOAD_API_KEY": "fload_sk_your_key_here" }
    }
  }
}

ChatGPT

1. In ChatGPT, add a custom connector (also called a custom MCP server).
2. Paste https://api.fload.com/mcp as the server URL and choose OAuth sign-in.
3. Sign in to Fload and click Allow.

Custom connectors depend on your ChatGPT plan. In Business, Enterprise and Edu workspaces, an admin may need to allow them first.

Cursor

Add Fload to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "fload": { "url": "https://api.fload.com/mcp" }
  }
}

Cursor opens the Fload sign-in the first time it connects.

VS Code (GitHub Copilot)

Add Fload to .vscode/mcp.json, or to your user configuration with the MCP: Open User Configuration command:

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

Start the server from the file, and VS Code opens the Fload sign-in. Then use Fload from Copilot's agent mode.

Any other MCP client

• Remote MCP with sign-in: use https://api.fload.com/mcp. The server speaks Streamable HTTP and OAuth 2.1, and registers your client on its own.
• Remote MCP with a key: send Authorization: Bearer fload_sk_… to the same URL. A key acts as the person who made it, with the key's own permissions. See API keys.
• No remote MCP: run the local MCP server with an API key.

How long you stay signed in

• A sign-in gives your AI app access for an hour at a time, and it renews itself in the background, so you don't notice.
• The connection stays signed in as long as it's used at least once every 30 days. After 30 days without use, you sign in again.
• Disconnect any app at any time under Settings › Connected Apps in Fload.
• An API key lasts until the expiry you picked (30 days, 90 days, a year or never) or until you revoke it.

What you approve when you sign in

The sign-in screen shows which app is asking, the account you're signed in with, and every permission it requests, each with a plain description. If you belong to more than one organization, you pick the one this app may use. Access never spans organizations.

An AI app or key without read:org can't see your team. It's told so, with how to fix it: the app asks for read:org when it connects, or you use a key with Read team and share links. Keys and connections made before 16 October 2026 with full access or every read permission keep seeing the team.

The sign-in also asks for openid, email, profile and offline_access, so the app knows who you are and stays connected between sessions.

How changes work

Agent setup

With Approve and run, your AI app can turn agents on or off, change when they run, retry a failed run, and edit, switch off or delete learned reply rules. With Reply to reviews it can change the Review Agent's settings, and with Propose ASO changes the ASO Agent's settings.

A few switches stay with people:

• Turning an agent on needs a signed-in app (this sign-in flow). An API key can't do it.
• Letting an agent act on its own needs your own sign-in plus Approve and run. That covers ASO auto mode, weekly promotional text and the Review Agent's Auto-mode. Anyone with access can turn them off.
• Review Agent settings can only be changed by a person: in Fload, or from an AI app you signed in to yourself.

Every tool

Generated from Fload's own tool list, so it matches what the server offers today. Each tool shows the permission your AI app needs for it. Tools marked "Goes to your inbox" wait for your approval before anything changes.

Credits

Reading data over MCP is free. Work that uses AI, such as drafting a reply, a chat message to Fio or a new report, costs the same credits as it does in the app. See Pricing & Credits.

Disconnect

Go to Settings → Connected Apps in Fload and remove the app. It's signed out straight away.

For agent authors and marketplace reviewers

Fload implements the MCP authorization specification: OAuth 2.1 with PKCE (S256) and dynamic client registration for public clients.

Discovery

• https://api.fload.com/.well-known/oauth-protected-resource: protected resource metadata (RFC 9728)
• https://api.fload.com/.well-known/oauth-authorization-server: authorization server metadata (RFC 8414)
• Mirrors at https://fload.com/.well-known/oauth-* for discovery from the apex domain

Endpoints

First contact

A request to https://api.fload.com/mcp without a token gets a 401 with:

WWW-Authenticate: Bearer resource_metadata="https://api.fload.com/.well-known/oauth-protected-resource"

Follow it to the authorization server, register a public client, run the authorization code flow with PKCE, and send resource=https://api.fload.com/mcp with the token request.

When a client connects, the server tells it how to work with Fload: call listAssets first and pass the app's id on every call; store data is complete up to two days ago; a missing value is unknown, not zero; and changes are staged in the inbox, not published.

Legal and contact

• Privacy policy
• Terms of service
• Support: support@fload.com