Browseract

Created By
BrowserAct5 months ago
BrowserAct MCP Server is a standardized service that lets MCP Clients interact with the BrowserAct platform through the Model Context Protocol (MCP). With it, MCP Clients can: Discover and execute browser automation workflows as MCP Tools Read outputs (results, files) and access related data storage Trigger real-world actions via natural language (e.g., send messages, create tasks, update records) Key Features 1. Multi-Scenario Support: Enables MCP Clients to run targeted tasks or complex searches across different applications 2. Natural Language Interaction: Describe what you need—no complex code or commands 3. Unlimited Tool Exposure: One MCP Server can expose unlimited MCP Tools 4. Multi-Client Compatibility: Works with Claude, ChatGPT, OpenAI Agent Builder, and other MCP-compatible clients
Overview

What is BrowserAct?

BrowserAct is an AI-powered web scraping and automation platform that allows users to interact with the BrowserAct platform through the Model Context Protocol (MCP). It enables clients to discover and execute browser automation workflows, read outputs, and trigger real-world actions using natural language.

How to use BrowserAct?

To use BrowserAct, set up the MCP Server and connect it with your preferred programming language (Python, Java, or Node.js). You can then run predefined or custom workflows by sending requests to the API endpoints.

Key features of BrowserAct?

  • Multi-Scenario Support: Run targeted tasks or complex searches across different applications.
  • Natural Language Interaction: Describe tasks in plain language without needing complex code.
  • Unlimited Tool Exposure: One MCP Server can expose unlimited MCP Tools.
  • Multi-Client Compatibility: Works with various MCP-compatible clients like Claude, ChatGPT, and OpenAI Agent Builder.

Use cases of BrowserAct?

  1. Automating data extraction from websites.
  2. Running complex searches across multiple applications.
  3. Triggering actions like sending messages or creating tasks through natural language commands.

FAQ from BrowserAct?

  • Can BrowserAct work with any website?

Yes! BrowserAct is designed to scrape data from any website, provided it complies with legal and ethical standards.

  • Is there a limit to the number of workflows I can create?

No, you can create as many workflows as needed, as the MCP Server can expose unlimited tools.

  • How do I secure my API key?

Use environment variables or secure configuration files to keep your API keys confidential.

Server Config

{
  "mcpServers": {
    "browseract": {
      "url": "<BROWSERACT_MCP_SERVER_URL>",
      "headers": {
        "Authorization": "Bearer <BROWSERACT_API_KEY>"
      }
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
BrowserAct
Star
-
Language
-
License
-
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago