{% include head-common.html %} {% include blog-styles.html %}

# Integrations

Tap is the layer between your AI agent and the websites it acts on. Compile a trajectory once; replay it forever at zero LLM tokens. These pages walk through the integration with each agent framework and host.

## Agent frameworks

LIVE

### browser-use

Compile an `AgentHistoryList` into a deterministic plan. Navigation skeleton (go_to_url, click, input, scroll, wait, done) replays at 0 LLM tokens. Tier 0 destinations also free for extraction.

ROADMAP

### Stagehand

Trajectory schema mapping for `act`, `extract`, and `observe` verbs. Same compile-once pattern; primitives overlap with browser-use so the lift is mostly schema. Vote on the issue.

ROADMAP

### Anthropic computer-use

Compile raw `tool_use` + `tool_result` trajectories. The screenshot-driven loop is heavier than DOM-driven trajectories; navigation skeleton still reduces deterministically once captured.

ROADMAP

### OpenAI computer-use

Same surface as Anthropic computer-use. Tracks the `computer_call` action shape. Coming after Anthropic lands.

## MCP hosts

Tap ships its own MCP server. Run `tap mcp connect` to auto-register with whichever host you use, or follow the host-specific notes:

LIVE

### Claude Code · Cursor · Cline · Windsurf

One `tap mcp connect` registers the server with all common MCP hosts. The blog post covers manual config for hosts that don't auto-discover.

LIVE

### MCP authoring patterns

Why MCP servers should expose compiled programs, not runtime prompts. The Tap MCP server's design rationale.

## What v1 compiles, plainly

Across every framework above, the v1 compile target is the same:

- Navigation skeleton (open URL, click, input, scroll, wait, done) — always replays at 0 LLM tokens.
- Extraction — replays at 0 LLM tokens at Tier 0 destinations (RSS, Atom, JSON-LD, agents.json, OpenAPI). Layer 4 DOM extraction still costs tokens; only the navigation half saves.
- Drift detection via `doctor` — runs independently of replay, against an authoritative source. Catches what a self-replay can't.

For an honest scope walk-through with token math, start with the browser-use page — the same shape applies to the other frameworks once the schema is mapped.