web-agent-protocol
MCP ServerFree🌐Web Agent Protocol (WAP) - Record and replay user interactions in the browser with MCP support
Capabilities11 decomposed
browser-interaction-recording-with-dom-state-capture
Medium confidenceRecords user interactions (clicks, typing, navigation) in a live browser session by instrumenting Playwright's event listeners and capturing DOM snapshots at each interaction point. Stores interaction sequences with full DOM state, element selectors, and coordinate data to enable deterministic replay and agent learning from human demonstrations.
Captures full DOM state alongside interaction metadata at each step, enabling agents to understand both the action taken and the resulting page state — most record-replay tools only store action sequences without semantic context
Provides richer training signal than simple action logs because agents can learn from DOM deltas and element state changes, not just coordinate-based clicks
deterministic-interaction-replay-with-selector-resolution
Medium confidenceReplays recorded interaction sequences by resolving stored selectors (CSS, XPath, or coordinate-based) against the current DOM and executing the corresponding Playwright actions (click, type, navigate). Handles selector drift by falling back to alternative selector strategies and validates element visibility/interactability before execution.
Implements multi-strategy selector resolution (CSS → XPath → coordinate fallback) with visibility validation, allowing replay to adapt to minor DOM changes rather than failing on first selector miss
More robust than coordinate-only replay (used by RPA tools) because it uses semantic selectors that survive layout changes, but more flexible than strict CSS matching by supporting fallback strategies
interaction-validation-and-assertion-framework
Medium confidenceProvides built-in assertions for validating interaction outcomes: element visibility, text content matching, URL changes, network request completion. Supports both immediate assertions (after each interaction) and deferred assertions (after workflow completion), enabling agents to verify that interactions succeeded and pages reached expected states.
Integrates assertions directly into interaction execution flow, allowing agents to validate outcomes inline rather than as separate test steps — enables reactive error handling based on assertion failures
More integrated than external test frameworks (like pytest) because assertions are part of the automation runtime, enabling real-time error recovery rather than post-execution failure reporting
mcp-server-integration-for-agent-tool-exposure
Medium confidenceExposes recording and replay capabilities as MCP (Model Context Protocol) tools that LLM agents can invoke through a standardized interface. Implements MCP server protocol with tool definitions for start-recording, stop-recording, and replay-interaction, allowing Claude, other LLMs, and agent frameworks to orchestrate browser automation without direct library imports.
Implements full MCP server protocol for browser automation, allowing stateless tool invocations from LLMs rather than requiring agents to manage browser session state directly — treats recording/replay as composable LLM-callable tools
Enables LLM agents to use web automation without custom integration code, unlike browser-use libraries that require agent framework-specific adapters
dom-aware-element-selection-with-multi-strategy-matching
Medium confidenceSelects elements for interaction using a cascading strategy: first attempts CSS selectors, falls back to XPath expressions, then uses coordinate-based selection as last resort. Validates element interactability (visibility, clickability) before returning and caches selector strategies that work for future reference, enabling robust element targeting across dynamic UIs.
Implements intelligent fallback chain with selector strategy caching — learns which selector type works for each element and reuses it, reducing retry overhead on subsequent interactions
More resilient than single-strategy selectors (pure CSS or XPath) because it adapts to DOM changes, but more performant than brute-force fuzzy matching because it caches successful strategies
interaction-sequence-composition-for-multi-step-workflows
Medium confidenceChains multiple recorded or programmatic interactions into a single executable workflow by composing interaction objects with dependency tracking and state validation between steps. Supports conditional branching based on page state (e.g., 'if element exists, click it; otherwise navigate') and error recovery strategies (retry with backoff, alternative action path).
Supports declarative workflow composition with state-based branching, allowing agents to define conditional paths without imperative control flow — workflows are data structures that can be generated by LLMs
More flexible than simple replay (which is linear) because it supports branching, but simpler than full workflow engines (like Zapier) because it's specialized for browser interactions
page-state-snapshot-and-diff-analysis
Medium confidenceCaptures full DOM snapshots at interaction points and computes diffs between consecutive states to identify what changed (new elements, removed elements, attribute changes, text content changes). Provides structured representation of page state changes that agents can reason about, enabling learning from state transitions rather than just action sequences.
Computes semantic diffs of DOM state (not just raw HTML diffs) by tracking element identity, attribute changes, and content mutations — enables agents to reason about 'what changed' at a semantic level
Richer than simple screenshot comparison (which is pixel-based and fragile) because it provides structured DOM-level changes that agents can reason about programmatically
playwright-browser-session-management-with-context-isolation
Medium confidenceManages Playwright browser instances, pages, and contexts with automatic lifecycle handling (launch, create page, close on error). Supports context isolation for parallel recording sessions and provides utilities for managing browser state (cookies, local storage, authentication) across interactions, enabling reproducible automation with consistent browser environment.
Provides context-aware session management that isolates recording sessions and preserves browser state, treating each recording as an independent experiment with its own browser context
More robust than manual Playwright usage because it handles cleanup and error cases automatically, and more flexible than headless browser services because it runs locally with full control
agent-learning-from-recorded-demonstrations
Medium confidenceConverts recorded interaction sequences into training examples for LLM agents by pairing interaction contexts (page state, user goal) with executed actions. Generates structured prompts that teach agents to recognize similar situations and execute appropriate interactions, supporting few-shot learning where agents learn from 1-5 demonstrations before generalizing to new tasks.
Structures demonstrations as context-action pairs with full DOM state, enabling agents to learn from semantic page understanding rather than just coordinate sequences — supports transfer learning across similar UIs
More effective than pure instruction-based agent prompting because agents learn from concrete examples, but requires less data than full supervised training because it uses few-shot learning
web-task-execution-with-natural-language-goals
Medium confidenceAccepts natural language task descriptions (e.g., 'log in with email and password, then navigate to settings') and translates them into executable interaction sequences using LLM reasoning. The system decomposes goals into sub-tasks, selects appropriate recorded interactions or generates new ones, and executes them with error handling and goal validation.
Combines recorded interaction library with LLM reasoning to handle both known tasks (via replay) and novel tasks (via LLM-generated interactions) — hybrid approach that leverages both demonstration and reasoning
More flexible than pure replay because it can handle novel tasks, but more reliable than pure LLM-based interaction generation because it can fall back to recorded demonstrations for known patterns
cross-browser-interaction-portability
Medium confidenceRecords interactions in a browser-agnostic format (semantic selectors, coordinate-independent actions) that can be replayed across different browsers (Chromium, Firefox, WebKit) without modification. Abstracts browser-specific APIs and handles rendering differences, enabling recorded workflows to work consistently regardless of browser engine.
Uses semantic selectors and browser-agnostic action primitives to enable replay across engines, rather than recording browser-specific commands — treats browser as implementation detail
More portable than Selenium-based automation (which is browser-specific) because Playwright abstractions are consistent across engines, but less portable than pure coordinate-based RPA because it uses semantic selectors
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with web-agent-protocol, ranked by overlap. Discovered automatically through the match graph.
Axiom
Streamline web tasks with no-code automation and AI...
Jam
Streamline bug reporting with automatic capture and cross-platform...
mcp-chrome
Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search.
Hyperbrowser
Browser infrastructure and automation for AI Agents and Apps with advanced features like proxies, captcha solving, and session recording.
Reflect.run
Automated regression testing,...
Hyperbrowser
Browser infrastructure and automation for AI Agents and Apps with advanced features like proxies, captcha solving, and session...
Best For
- ✓AI agent developers building web automation systems
- ✓Teams creating training datasets for browser-based LLM agents
- ✓QA engineers automating complex multi-step web workflows
- ✓Automation engineers building regression test suites from recorded workflows
- ✓LLM agent systems that need to execute learned interaction patterns
- ✓Teams validating web application stability across UI iterations
- ✓QA automation engineers building reliable test suites
- ✓LLM agent systems that need to validate action outcomes
Known Limitations
- ⚠Recording adds overhead to browser session — captures full DOM at each step which can be memory-intensive for long sessions
- ⚠Cannot record interactions in iframes or cross-origin contexts due to browser security restrictions
- ⚠Selector stability depends on DOM structure — dynamic or frequently-changing UIs may produce unreliable replay selectors
- ⚠Replay fails if selectors become invalid due to DOM restructuring — requires manual selector updates or fuzzy matching
- ⚠Timing-sensitive interactions (rapid clicks, drag operations) may not replay identically due to network/rendering delays
- ⚠Cannot replay interactions that depend on external state (file uploads, camera access) without mocking
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
Repository Details
Last commit: Jun 19, 2025
About
🌐Web Agent Protocol (WAP) - Record and replay user interactions in the browser with MCP support
Categories
Alternatives to web-agent-protocol
Are you the builder of web-agent-protocol?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →