Connect clients

All clients use the same address:

MCP server address

https://lantfly.com/mcp

Clients with MCP OAuth need nothing else: they open a Lantfly page where you sign in, pick the account and click Allow. Clients without OAuth send an API token instead.

OAuth (recommended)

Claude

Works in Claude on the web and in Claude Desktop.

1. Open Settings → Connectors.
2. Click Add custom connector.
3. Enter a name (for example Lantfly) and paste https://lantfly.com/mcp as the URL.
4. Click Connect. Claude opens Lantfly: sign in, pick the account, choose read-only if you like, and click Allow.
5. In a chat, enable the Lantfly connector from the tools menu and ask away.

Claude Code

1. Add the server:

   Terminal

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

2. Start Claude Code and run /mcp. Pick lantfly and choose to authenticate. Your browser opens Lantfly: sign in, pick the account and click Allow.

3. Back in Claude Code, /mcp shows lantfly as connected.

Add --scope user to use the server in every project, or --scope project to share it with your team through .mcp.json.

ChatGPT

1. In ChatGPT, open Settings → Apps & Connectors and turn on Developer mode (under advanced settings).
2. Create a connector: give it a name, paste https://lantfly.com/mcp as the server URL, and choose OAuth authentication.
3. ChatGPT opens Lantfly: sign in, pick the account and click Allow.
4. In a chat, add the connector from the tools menu.

Availability of developer mode and custom connectors depends on your ChatGPT plan.

Cursor

1. Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

   ~/.cursor/mcp.json

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

2. Open Cursor Settings → MCP. Cursor shows lantfly and asks you to log in: sign in to Lantfly, pick the account and click Allow.

VS Code

For GitHub Copilot agent mode in VS Code.

1. Create .vscode/mcp.json in your workspace:

   .vscode/mcp.json

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

2. Click Start above the server in the file. VS Code opens Lantfly: sign in, pick the account and click Allow.

3. In Copilot Chat, switch to Agent mode and enable the Lantfly tools from the tools picker.

tip

When the consent page asks, tick Read-only for an assistant that should only look: it can search actors and read runs, results and listening data, but can't start runs or change anything.

API token

Use this when a client has no MCP OAuth, for servers and CI, or when you want a scoped token (for example limited to one actor or to listening.read). Create the token under Settings → API & integrations in the Console.

Claude Code

Terminal

claude mcp add --transport http lantfly https://lantfly.com/mcp \
  --header "Authorization: Bearer $LANTFLY_TOKEN"

Cursor

~/.cursor/mcp.json

{
  "mcpServers": {
    "lantfly": {
      "url": "https://lantfly.com/mcp",
      "headers": { "Authorization": "Bearer <your API token>" }
    }
  }
}

VS Code

VS Code prompts for the token once and stores it securely:

.vscode/mcp.json

{
  "inputs": [
    { "type": "promptString", "id": "lantfly-token", "description": "Lantfly API token", "password": true }
  ],
  "servers": {
    "lantfly": {
      "type": "http",
      "url": "https://lantfly.com/mcp",
      "headers": { "Authorization": "Bearer ${input:lantfly-token}" }
    }
  }
}

Claude Desktop (local)

Claude Desktop's config file starts local (stdio) servers. Bridge to Lantfly with mcp-remote, which needs Node.js. Edit claude_desktop_config.json (Settings → Developer → Edit Config):

claude_desktop_config.json

{
  "mcpServers": {
    "lantfly": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://lantfly.com/mcp", "--header", "Authorization:${LANTFLY_AUTH}"],
      "env": { "LANTFLY_AUTH": "Bearer <your API token>" }
    }
  }
}

Restart Claude Desktop. Putting the header value in env avoids a space inside args, which some systems split.

Other clients

Any client that speaks MCP over Streamable HTTP works:

Setting	Value
Transport	Streamable HTTP (sometimes called http)
URL	https://lantfly.com/mcp
Header	Authorization: Bearer <your API token>
Organization (optional)	X-Lantfly-Account: <organization id>

If the client can't set headers, put the token in the URL: https://lantfly.com/mcp?token=<your API token>.

If the client only starts local (stdio) servers, use mcp-remote as shown for Claude Desktop:

stdio bridge

npx -y mcp-remote https://lantfly.com/mcp --header "Authorization:Bearer $LANTFLY_TOKEN"

warning

A token in a config file or URL is a secret. Don't commit it; prefer a scoped token, and regenerate it if it leaks.

Act for an organization

• OAuth: pick the organization on the consent page. To use another organization, connect the app again and pick it. An OAuth connection can't switch accounts with a header.
• API token: add X-Lantfly-Account: <organization id> to the headers, or use a token created while you act for the organization. See Organizations.

Give an actor its own tool

Add ?actors= with up to 20 actor slugs or IDs, comma separated, and each becomes a tool whose arguments are that actor's input:

Address with two actor tools

https://lantfly.com/mcp?actors=lantfly~tiktok-scraper,lantfly~web-scraper

The tools are named after the slug with ~ replaced by --, for example lantfly--tiktok-scraper. The AI & MCP page in the Console builds this address for you under Actors as their own tools. See Per-actor tools.

Check the connection

Ask the assistant "Which Lantfly tools do you have?", or call the server yourself:

List tools

curl https://lantfly.com/mcp \
  -H "Authorization: Bearer $LANTFLY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

If something fails, see Troubleshooting.