# WebUplink [Health: Active]

**Category:** 📂 Browser Automation  
**Repository:** https://github.com/webuplink-dev/webuplink-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/webuplink

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

## Tools
Capabilities this server exposes over MCP:

- **browse** — Browse a web page or execute tools on a page.
- **close_session** — Close a browser session to free resources.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "webuplink": {
    "command": "npx",
    "args": ["--yes","--package","@webuplink/mcp","webuplink-mcp-http"]
  }
}
```

## Documentation & README

<picture>
  <source media="(prefers-color-scheme: dark)" srcset=".github/logo-dark.svg">
  <source media="(prefers-color-scheme: light)" srcset=".github/logo-light.svg">
  <img alt="WebUplink" src="https://raw.githubusercontent.com/webuplink-dev/webuplink-mcp/HEAD/.github/logo-light.svg" width="200">
</picture>

### MCP server for WebUplink

[![npm version](https://img.shields.io/npm/v/@webuplink/mcp.svg)](https://www.npmjs.com/package/@webuplink/mcp)
[![CI](https://github.com/webuplink-dev/webuplink-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/webuplink-dev/webuplink-mcp/actions)
[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)

Give any MCP client the ability to browse and interact with the web via [WebUplink](https://webuplink.ai).

## 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.

| 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:

```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