Installation and setup

This setup flow gets you from zero to a working bridge in under ten minutes.

Prerequisites

• Chromium-based browser with extension support.
• Node.js 18+ for local MCP tooling.
• Access to a SaaS dashboard where your user account is already signed in.

1. Install the extension

1. Install the Jumper extension package.
2. Open the target SaaS dashboard tab.
3. Confirm the extension is active for the tab.

When active, Jumper can inspect page structure and bind mapped values to tool parameters.

2. Define your bridge schema

Create a jumper.config.json file:

{
  "version": "1.0",
  "target": "https://app.example-saas.com",
  "mcp_server": "ws://localhost:8080/mcp",
  "mappings": [
    {
      "mcp_param": "customer_id",
      "selector": ".profile-header .id-badge",
      "extract": "text"
    },
    {
      "mcp_param": "status_active",
      "selector": "div[data-status='active']",
      "extract": "attribute",
      "attribute_name": "data-status"
    }
  ]
}

3. Load and test configuration

1. Open Jumper settings.
2. Paste or import your configuration.
3. Save and run a test extraction against the active page.

Expected result:

• You see extracted values in the console.
• The payload is delivered to your MCP endpoint.

4. Run your local bridge service

jumper start --config ./jumper.config.json

If port 8080 is already used, switch to another local port and update your config.

Troubleshooting checklist

• Selector returns nothing: test selector against the current rendered DOM.
• Payload fields empty: verify extract mode and attribute names.
• Connection errors: verify ws endpoint, firewall, and local process state.

Continue with Architecture for the system-level model.