Tapicker Bridge

Tapicker Bridge connects external tools and AI agents to a Tapicker browser Extension. Use it to run and control Workflows, access extracted data, or receive Workflow status updates through the CLI, HTTP, or MCP.

The Bridge routes commands; browser automation runs in the connected Tapicker Extension.

Quick Start

Requirements: Node.js 22 or later and the Tapicker Extension installed in a supported browser.

npm install --global @tapicker/bridge
tapicker bridge start

Keep the terminal open. Bridge prints a WebSocket endpoint and a four-digit pairing code. In the Extension, open Settings > General, enable Bridge, then click Scan or enter the endpoint and click Connect. Enter the pairing code when prompted.

Copy a Workflow ID in Tapicker and run it:

tapicker workflow start <workflowId> --watch

Bridge listens on 127.0.0.1 by default and tries ports 9520–9530. If it selects a port other than 9520, pass the actual port with --port to CLI commands.

Learn the User Flows

• Getting Started — install Bridge, pair an Extension, and run your first Workflow.
• Control Workflows — start, pause, resume, stop, and watch Workflows.
• Connect an AI Agent — use MCP or the HTTP API.
• Remote Deployment — configure TLS and a Bearer Token.
• API Reference — CLI commands, HTTP endpoints, MCP tools, and status events.

Documentation in This Package

• CLI reference
• HTTP API reference
• MCP setup and tools
• Pairing, configuration, and security
• Workflow status WebSocket

Security

Keep Bridge on its default loopback address unless remote access is required. Local mode has no Bearer Token by default, and HTTP CORS defaults to *; restrict --cors-origin when browser pages should not access the local API. Non-loopback binding requires TLS and a Bearer Token.

Bridge does not manage Tapicker accounts. See the remote deployment guide before exposing it to a network.