abrasio-mcp

Purpose: Enabling AI models to interact with the web through an agentic browser interface.

Inferred · not functionally tested

Audience: AI researchers and developers building autonomous agents

Inferred · not functionally tested

Functions: browser_automation, agents

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, api_only, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

In the Frameworks & runtimes space, abrasio-mcp takes a focused approach. Inferred · not functionally tested: It focuses on enabling AI models to interact with the web through an agentic browser interface. Inferred · not functionally tested: It is built as an open-source project for AI researchers and developers building autonomous agents. Basis unknown · not verified: abrasio-mcp is open source under the MIT license. Basis unknown · not verified: It ships for the command line and API, and it can be self-hosted.

Behind abrasio-mcp is Scrape Technology, and it first shipped in 2026. Development happens publicly on GitHub with 3 commits in the last 90 days. Inferred · not functionally tested: Among its 5 catalogued features are MCP server, agentic browser, and AI model integration. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.