Skip to main content
Glama
@webuplink/mcp

@webuplink/mcp

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:

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

Related MCP server: Cloudflare Playwright MCP

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

Available Tools

2 tools
browseB

Browse a web page or execute tools on a page. Use url to open a new session, or session_id to continue an existing session.

Inputs: url, tool, tools, params, +2 more.

close_sessionA

Close a browser session to free resources. Sessions auto-expire after 5 minutes of inactivity, but explicit cleanup is recommended.

Inputs: session_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: browse handles opening or continuing a session and interacting with pages, while close_session explicitly handles teardown and resource cleanup. There is no overlap between them, so an agent should not confuse which tool to call.

    Naming Consistency4/5

    Both tool names use imperative verbs, which is coherent, but browse is a bare verb while close_session follows a verb_noun pattern. The inconsistency is minor given the very small tool set, but a more consistent name like browse_page would improve the pattern.

    Tool Count3/5

    At two tools, the server feels thin for what appears to be a web browsing or browser automation domain. The two tools do form a minimal session lifecycle, so the count is borderline rather than obviously wrong, but it likely underrepresents the full range of browsing actions an agent might need.

    Completeness3/5

    The core lifecycle of opening/continuing a session with browse and closing it with close_session is covered, but there is no explicit session listing or status tool, and the browse tool appears to absorb many possible page actions into one generic entry point. Agents may be able to work around the gaps, but the surface is notably sparse for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      Apache 2.0
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      Apache 2.0
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      Apache 2.0