WebUplink
Give any MCP client the ability to browse and interact with the web via WebUplink.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@webuplink/mcpclaude mcp add webuplink -e 'WEBUPLINK_API_KEY=<your webuplink_api_key>' -- npx -y @webuplink/mcp@0.1.1
{
"mcpServers": {
"webuplink": {
"command": "npx",
"args": [
"-y",
"@webuplink/mcp@0.1.1"
],
"env": {
"WEBUPLINK_API_KEY": "<your webuplink_api_key>"
}
}
}
}
Environment variables
WEBUPLINK_API_KEYrequired secret Your WebUplink API key
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
MCP server for WebUplink
Give any MCP client the ability to browse and interact with the web via WebUplink.
Claude Desktop
Add to claude_desktop_config.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:
{
"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.
| Parameter | Type | Description |
|---|---|---|
url | string | URL to open a new browser session |
session_id | string | Existing session ID to continue browsing |
tool | string | Tool name to execute on the page |
params | object | Parameters for the tool |
include_page_content | boolean | Include detailed page content |
close_session
Close a browser session to free resources.
| Parameter | Type | Description |
|---|---|---|
session_id | string | Session ID to close |
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
WEBUPLINK_API_KEY | ✅ | — | Your WebUplink API key |
WEBUPLINK_BASE_URL | — | https://api.webuplink.ai | API base URL |
PORT | — | 3001 | Local HTTP transport port |
MCP_HTTP_HOST | — | 127.0.0.1 | Local HTTP transport bind address |
MCP_HTTP_ALLOWED_HOSTS | non-loopback HTTP only | loopback names | Comma-separated Host/Origin names accepted by the HTTP boundary |
HTTP Transport
For a local Streamable HTTP endpoint, invoke the HTTP binary explicitly:
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:
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
Frequently asked questions
What is WebUplink?
Give any MCP client the ability to browse and interact with the web via WebUplink.
How do I install WebUplink?
It runs on your machine. In Claude Code: claude mcp add webuplink -e 'WEBUPLINK_API_KEY=<your webuplink_api_key>' -- npx -y @webuplink/mcp@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does WebUplink need an API key?
Yes. It expects WEBUPLINK_API_KEY, which you set in its configuration.
Is WebUplink open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains WebUplink?
It is published by webuplink-dev. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.