Highway MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port when TRANSPORT=http | 8848 |
| TRANSPORT | No | Transport type: stdio or http/streamable-http | stdio |
| HIGHWAY_API_KEY | Yes | hw_k1_... key, forwarded as Bearer | |
| HIGHWAY_BASE_URL | No | Engine base URL | http://localhost:7822 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_goalA | Start a durable Highway agent that pursues Returns immediately with a workflow_run_id. The agent runs server-side and survives this client disconnecting. Use get_status to follow it and to see any actions awaiting your approval. |
| get_statusA | Get an agent run's status, progress, result, and any pending approvals.
|
| approveA | Approve (or reject) a pending agent action to resume the durable run. Set approved=False to reject. This works across sessions and devices: you can approve from one client an action a run started from another. |
| schedule_goalA | Schedule an agent to run cron_expression is standard 5-field cron in UTC, e.g. '0 9 * * ' = daily 09:00, '/30 * * * *' = every 30 minutes. The scheduled agent runs WITHOUT per-run human approval (creating the schedule is the authorization), so only schedule goals you trust. Uses Highway's durable cron (survives restarts; no history bloat). Returns the schedule details. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: 'approve' handles pending actions, 'get_status' tracks run progress, 'run_goal' starts a new run, and 'schedule_goal' sets up recurring runs. No overlap or ambiguity.
Three tools follow a clear verb_noun pattern (get_status, run_goal, schedule_goal), but 'approve' omits the noun. The pattern is mostly consistent and readable, with a minor deviation.
Four tools is well-scoped for the server's purpose of managing durable agent runs with approvals. Each tool is essential and the set is concise without being sparse.
The tools cover starting, scheduling, checking status, and approving runs, but missing cancellation or deletion capabilities (e.g., cancel_run, delete_schedule) are notable gaps that agents may need.