Babelwrap Mcp

io.github.soulfirPublished by GitHub account soulfirv0.1.1Updated Oct 24, 2026

Let AI agents interact with any website through natural language instead of CSS selectors

VerifiedSTDIODesktop onlyWeb Search & ScrapingBrowser Automation

Overview

AI-generated overview

Local MCP server that lets an assistant drive a web browser through the BabelWrap API using natural language instead of CSS selectors.

What you can do
  • Create, close and switch between browser sessions and tabs
  • Navigate to URLs, go back and forward, scroll, and wait for page conditions
  • Inspect the current page state and take screenshots
  • Click, hover, fill and submit forms, press keys, and upload files
  • Extract structured data from pages
When to use it
Useful when an assistant needs to browse or operate websites on the user's behalf — filling forms, clicking through flows, capturing screenshots or pulling structured data — without writing selectors by hand.
Requirements
Runs as a local process, installed via uvx, pip or pipx (Python). Requires a BabelWrap account and an API key supplied in the BABELWRAP_API_KEY environment variable; an optional BABELWRAP_API_URL overrides the API base URL. Network access to the BabelWrap API is needed.
Before you install
The API key is a secret passed in plain text through the client configuration or environment. The server can click, fill, submit forms and upload files on live websites, so actions may change or send data on third-party sites, and page content and browsing activity pass through the BabelWrap API. Usage may be subject to BabelWrap account limits or billing.

Installation

In SourceWeft

  1. Open Babelwrap Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

BabelWrap MCP Server

An MCP server that gives AI agents web browsing superpowers via the BabelWrap API.

Works with Claude Desktop, Cursor, Claude Code, and any MCP-compatible client.

Installation

bash
# Using uvx (recommended -- no install required)uvx babelwrap-mcp
# Using pippip install babelwrap-mcp
# Using pipx (isolated environment)pipx install babelwrap-mcp

Setup

1. Get an API Key

Sign up at babelwrap.com and create an API key from your dashboard.

2. Configure Your MCP Client

Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "babelwrap": {      "command": "uvx",      "args": ["babelwrap-mcp"],      "env": {        "BABELWRAP_API_KEY": "bw_your_api_key_here"      }    }  }}

If you installed with pip or pipx, use the binary directly:

json
{  "mcpServers": {    "babelwrap": {      "command": "babelwrap-mcp",      "args": [],      "env": {        "BABELWRAP_API_KEY": "bw_your_api_key_here"      }    }  }}
Claude Code
bash
claude mcp add babelwrap -- uvx babelwrap-mcp

Then set your API key as an environment variable:

bash
export BABELWRAP_API_KEY="bw_your_api_key_here"

Available Tools

ToolDescription
babelwrap_new_sessionCreate a new browser session
babelwrap_close_sessionClose a browser session
babelwrap_navigateNavigate to a URL
babelwrap_snapshotGet current page state
babelwrap_clickClick an element
babelwrap_fillFill a form field
babelwrap_submitSubmit a form
babelwrap_extractExtract structured data
babelwrap_screenshotTake a screenshot
babelwrap_pressPress a keyboard key
babelwrap_scrollScroll the page
babelwrap_hoverHover over an element
babelwrap_uploadUpload a file
babelwrap_back / babelwrap_forwardBrowser history
babelwrap_wait_forWait for a condition
babelwrap_list_pages / babelwrap_switch_pageMulti-tab support

Environment Variables

VariableRequiredDescription
BABELWRAP_API_KEYYesYour BabelWrap API key
BABELWRAP_API_URLNoAPI base URL (default: https://api.babelwrap.com/v1)

Documentation

Full documentation at babelwrap.com/docs/mcp

License

MIT

Source: README.md at commit 094862f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts