WebUplink

ai.webuplinkPublished by webuplink.aiv0.1.1Updated Nov 10, 2026

Give any MCP client the ability to browse and interact with the web via WebUplink.

VerifiedSTDIODesktop onlyBrowser Automation

Overview

AI-generated overview

WebUplink lets an MCP client open web pages in a hosted browser session and run page tools on them, then close the session.

What you can do
  • Browse a web page by URL, starting a new browser session
  • Continue an existing session and execute named tools on the page with parameters
  • Optionally request detailed page content in the response
  • Close a browser session to free resources
When to use it
Useful when an assistant needs to open real websites, interact with page elements, or pull page content through a managed browsing service rather than plain fetching.
Requirements
Runs locally via npx from the npm package @webuplink/mcp (Node.js required). Needs a WebUplink API key in WEBUPLINK_API_KEY. Optional settings: WEBUPLINK_BASE_URL, PORT, MCP_HTTP_HOST, MCP_HTTP_ALLOWED_HOSTS. An HTTP transport binary is also available, listening on 127.0.0.1:3001 by default.
Before you install
The API key is a secret sent to the WebUplink service, and browsing activity goes through that third party. The HTTP transport has no client authentication: every accepted request uses the single configured API key, so do not expose the listener to an untrusted network and put an authenticated boundary in front of it for remote use. Page tools may act on websites.

Installation

In SourceWeft

  1. Open WebUplink 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

[WebUplink]

MCP server for WebUplink

[npm version] [CI] [License: MIT]

Give any MCP client the ability to browse and interact with the web via WebUplink.

Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "webuplink": {      "command": "npx",      "args": ["--yes", "--package", "@webuplink/mcp", "webuplink-mcp"],      "env": {        "WEBUPLINK_API_KEY": "wup_your_api_key"      }    }  }}

Cursor

Add to .cursor/mcp.json:

json
{  "mcpServers": {    "webuplink": {      "command": "npx",      "args": ["--yes", "--package", "@webuplink/mcp", "webuplink-mcp"],      "env": {        "WEBUPLINK_API_KEY": "wup_your_api_key"      }    }  }}

That's it — your AI can now browse and interact with any website.

Tools

browse

Browse a web page or execute tools on a page.

ParameterTypeDescription
urlstringURL to open a new browser session
session_idstringExisting session ID to continue browsing
toolstringTool name to execute on the page
paramsobjectParameters for the tool
include_page_contentbooleanInclude detailed page content

close_session

Close a browser session to free resources.

ParameterTypeDescription
session_idstringSession ID to close

Environment Variables

VariableRequiredDefaultDescription
WEBUPLINK_API_KEY✅—Your WebUplink API key
WEBUPLINK_BASE_URL—https://api.webuplink.aiAPI base URL
PORT—3001Local HTTP transport port
MCP_HTTP_HOST—127.0.0.1Local HTTP transport bind address
MCP_HTTP_ALLOWED_HOSTSnon-loopback HTTP onlyloopback namesComma-separated Host/Origin names accepted by the HTTP boundary

HTTP Transport

For a local Streamable HTTP endpoint, invoke the HTTP binary explicitly:

bash
WEBUPLINK_API_KEY=wup_... npx --yes --package @webuplink/mcp webuplink-mcp-http

The server accepts stateless MCP POST requests at /mcp and listens on 127.0.0.1:3001 by default. Set PORT to change the port.

Binding to a non-loopback interface is an explicit opt-in:

bash
WEBUPLINK_API_KEY=wup_... MCP_HTTP_HOST=0.0.0.0 \  MCP_HTTP_ALLOWED_HOSTS=mcp.internal.example \  npx --yes --package @webuplink/mcp webuplink-mcp-http

The listener rejects missing or unlisted Host headers before allocating MCP resources and applies the same allowlist to browser Origin headers. This protects the loopback default from DNS rebinding; it is not client authentication. Every accepted request still uses the single configured WEBUPLINK_API_KEY, so do not expose the listener directly to an untrusted network. Put an authenticated boundary in front of it for controlled remote use.

License

MIT

Source: README.md at commit c207ad3

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