@webuplink/mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@webuplink/mcp Browse to webuplink.ai and summarize the page."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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"
}
}
}
}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 |
| string | URL to open a new browser session |
| string | Existing session ID to continue browsing |
| string | Tool name to execute on the page |
| object | Parameters for the tool |
| boolean | Include detailed page content |
close_session
Close a browser session to free resources.
Parameter | Type | Description |
| string | Session ID to close |
Environment Variables
Variable | Required | Default | Description |
| ✅ | — | Your WebUplink API key |
| — |
| API base URL |
| — |
| Local HTTP transport port |
| — |
| Local HTTP transport bind address |
| 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-httpThe 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-httpThe 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 toolsbrowseB
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
Scored across 2 tools
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.
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.
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.
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
Related MCP Connectors
Control a real browser from AI agents: navigate, click, type, screenshot, read the page.
Let your AI agent operate any website through a real, logged-in browser session.
A real browser for your agent: screenshots, page checks, Markdown and PDFs.
Hosted browser for agents: open pages, search the web, extract data, read PDFs and take screenshots.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables 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
- AlicenseNot gradedqualityNot gradedmaintenanceEnables 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
- AlicenseNot gradedqualityNot gradedmaintenanceEnables 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
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to control a browser for web automation tasks like navigation, typing, clicking, and taking screenshots.Apache 2.0