Airtop MCP Server

An MCP server to talk to Airtop (https://www.airtop.ai/). Exposed over MCP by the airtop mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol (MCP) server that provides tools for interacting with Airtop's browser automation service.

Its toolset

Everything the assistant can do here goes through one of these:

• createSession — Create a new Airtop browser session
• createWindow — Create a new browser window in the session
• pageQuery — Query the current page content using AI
• terminateSession — Terminate an Airtop browser session
• paginatedExtraction — Extract data from a paginated list
• Development — 1. Clone the repository 2. Install dependencies: bash npm install 3. Set your Airtop API key: bash export AIRTOP_API_KEY=your_api_key_here 4. Start

Configuration

You will need one environment variable: AIRTOP_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Airtop's toolset — createSession, createWindow, pageQuery and 3 more — is a fair guide to whether it matches your workflow. It is maintained by alecf; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Airtop's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the airtop mcp server does with a few real requests.