AutoBrowser MCP

Created By
autobrowser-aia year ago
Autobrowser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
Overview

What is AutoBrowser MCP?

AutoBrowser MCP is a Model Context Provider (MCP) server that enables AI applications to control your browser seamlessly.

How to use AutoBrowser MCP?

To use AutoBrowser MCP, integrate it with your AI application by following the documentation provided on the official website and GitHub repository.

Key features of AutoBrowser MCP?

  • Allows AI applications to interact with web browsers.
  • Provides a flexible API for browser control.
  • Supports various AI-driven tasks and automation.

Use cases of AutoBrowser MCP?

  1. Automating web scraping tasks using AI.
  2. Enhancing user experience by automating repetitive browser actions.
  3. Integrating AI chatbots that can browse the web for information.

FAQ from AutoBrowser MCP?

  • What is the purpose of AutoBrowser MCP?

AutoBrowser MCP is designed to facilitate AI applications in controlling web browsers for various tasks.

  • Is AutoBrowser MCP free to use?

Yes! AutoBrowser MCP is open-source and available for free on GitHub.

  • Where can I find the documentation?

Documentation is available at https://docs.autobrowser.ai.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
autobrowser-ai
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Gpt Scrambler

2 days 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.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago