INDIVIDUAL MCP TOOL

pilotage_get_guide

Guides for a Language.

pilotagespec.orgnone authenticationAvailability not checked

LIVE ENDPOINT

https://harborview.pilotagespec.org/mcp

No auth detected

Connect to this endpoint to inspect the live schema for pilotage_get_guide and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.harborview]
url = "https://harborview.pilotagespec.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "harborview": {
      "type": "http",
      "url": "https://harborview.pilotagespec.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: harborview
Remote MCP URL: https://harborview.pilotagespec.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "harborview": {
      "url": "https://harborview.pilotagespec.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "harborview": {
      "type": "http",
      "url": "https://harborview.pilotagespec.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "harborview",
  "transport": "streamable-http",
  "url": "https://harborview.pilotagespec.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

pilotage_manifest — The Pilotage manifest: languages, capabilities, and the loop tool names.
pilotage_catalog — The live catalog: devices and promoted automations.
validate_flow — Check a buildingflow/1 document without side effects.
run_flow — Execute a buildingflow/1 document (inline 'flow') or a promoted automation ('program_ref').
trace_run — Fetch a past buildingflow/1 run from its stored record: the recorded outcome, output, and the trace with branch decisions.
promote_flow — Engine feature (not part of the Pilotage loop): store a valid flow as a reusable catalog entry, run on demand via program_ref.
world_status — Demo harness: the simulated building's current state (clock, occupancy, devices, deployed automations).
world_advance — Demo harness: drive the simulation.