Highway Agents

MCP Endpoint

A hosted Model Context Protocol server for authoring, running, and approving durable, always-on AI automations on Highway — from any MCP host (Claude, opencode, Cursor, mobile). No infrastructure to run on your side.

Endpoint: https://mcp.highway.rodmena.app/mcp · Transport: streamable-http · Auth: Bearer API key

Connect your MCP client

Add the server URL and your Highway API key as an Authorization: Bearer header. A generic MCP client config:

{
  "mcpServers": {
    "highway": {
      "type": "http",
      "url": "https://mcp.highway.rodmena.app/mcp",
      "headers": { "Authorization": "Bearer hw_k1_YOUR_KEY_HERE" }
    }
  }
}

Claude Code (CLI):

claude mcp add --transport http highway https://mcp.highway.rodmena.app/mcp \
  --header "Authorization: Bearer hw_k1_YOUR_KEY_HERE"

Where do I put my API key & tenant?

Only the API key, and only in your client (the header above). You do not set a tenant id — Highway derives your tenant from the key. One key = one tenant. Get a key (hw_k1_…) from your Highway dashboard.

Tools

run_goalStart a durable agent that pursues a natural-language goal to completion. Returns a workflow_run_id; the agent keeps running server-side even after you disconnect.
get_statusGet a run's status, progress, result, and any actions awaiting your approval.
approveApprove or reject a paused action to resume the run — works across devices.
schedule_goalRun a goal on a recurring cron schedule (e.g. a daily report email), unattended.

How it works

  1. Author in plain English via run_goal / schedule_goal.
  2. The agent runs durably on Highway — it survives restarts and client disconnects.
  3. Outbound/risky actions pause for your approval (human-in-the-loop); approve from any device with approve.
  4. Monitor anytime with get_status.