About WebUplink
WebUplink is an MCP server that lets AI clients browse and interact with websites. Its tools open browser sessions, run page actions, return page content, and close sessions.
Key features
- 01Browse web pages
- 02Run tools on a page
- 03Continue existing sessions
- 04Include page content
- 05Close browser sessions
Use cases
- 01Browse a page from an AI client
- 02Run available actions on a website
- 03Continue work in an existing browser session
- 04Release browser resources after use
MCP support
Exposes browsing and session-management tools to MCP clients. It supports stdio configuration and a local Streamable HTTP endpoint.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
2Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| url | string | No | URL to open a new browser session |
| tool | string | No | Tool name to execute on the page |
| tools | array | No | Array of tools to execute in sequence (batch) |
| params | object | No | Parameters for the tool |
| session_id | string | No | Existing session ID to continue browsing |
| include_page_content | boolean | No | Include detailed page content analysis |
Details
From the project READMEMCP 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.