MCP Server

WebUplink is MCP-native: it ships an MCP (Model Context Protocol) server, so it drops into any MCP-compatible AI agent — Claude, Cursor, and others — over the same web-actions endpoint.

Installation

The MCP server is available as the @webuplink/mcp package:

npm install @webuplink/mcp

Configuration

Add WebUplink to your MCP configuration:

{
  "mcpServers": {
    "webuplink": {
      "command": "npx",
      "args": ["@webuplink/mcp"],
      "env": {
        "WEBUPLINK_API_KEY": "wup_your_key_here",
        "WEBUPLINK_BASE_URL": "https://api.webuplink.ai"
      }
    }
  }
}

Available Tools

The MCP server registers two generic tools:

A page's own actions — search_hotels, open_invoice, login, and so on — are not registered as individual MCP tools. They come back as data inside the browse result (the PageMap's tool list), and your agent invokes one with a second browse call that passes the tool name and its params. So the MCP tool list always shows browse and close_session; the per-page tools are discovered at runtime from each page.