Draftlink

Documentation map

The docs portal stays in the same application as the product shell so setup, deployment, connector, and developer guidance can evolve with the codebase.

In-repo docs7 foundation routes5 developer routesCurrent: MCP Guide

Foundation docs

OverviewRoute
Start with the current architecture, product surfaces, and the stable documentation sections.
Getting StartedRoute
Install the workspace, configure local env files, and run the first verification flow.
DeploymentRoute
Use the managed bridge deployment order, health checks, migrations, and workspace bootstrap flow.
ConnectorsRoute
Understand the Figma reference connector, Satellite runtime, and explicit session routing model.
SecurityRoute
Review auth lanes, workspace isolation, policy controls, rate limiting, and audit semantics.
API ReferenceRoute
Browse the stable HTTP route groups, shared envelopes, auth lanes, and machine-readable errors.
TroubleshootingRoute
Use the current operational failure patterns for readiness, auth, session liveness, policy, and MCP issues.

Developer docs

DevelopersRoute
Developer-facing entry point for HTTP, MCP, connector, and shared-contract guidance.
Developer QuickstartRoute
Bring up the bridge, connect one runtime, and make the first explicit authenticated calls.
HTTP GuideRoute
Use the bridge HTTP transport with the correct auth lane, shared envelopes, and explicit targetSessionId routing.
MCP GuideOpen
Use the Streamable HTTP MCP endpoint, LIST_CAPABILITIES, and the same connector-neutral tool catalog.
Connector ModelRoute
Understand connector definitions, capability metadata, data scopes, and high-risk policy presets.

Transport contract

MCP uses the bridge's authenticated HTTP endpoint and then maps tool calls into the shared controller.

POST /mcpAuthorization: Bearer <api-key>Streamable HTTP MCP

LIST_CAPABILITIES call

JSON

{
  "jsonrpc": "2.0",
  "id": "list-capabilities-1",
  "method": "tools/call",
  "params": {
    "name": "LIST_CAPABILITIES",
    "arguments": {
      "connectorType": "satellite"
    }
  }
}

Tool call with routing

JSON

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "SATELLITE_ECHO",
    "arguments": {
      "workspaceId": "<workspace-id>",
      "targetSessionId": "satellite-session-1",
      "text": "hello"
    }
  }
}

Routing and secure-path behavior

MCP tool arguments merge the normal tool input with workspaceId and targetSessionId so routing stays explicit.

Tool inventory shape

The MCP server registers LIST_CAPABILITIES plus the same connector command catalog that HTTP execution uses.

SATELLITE_COMMAND_DESCRIPTOR

preview / mediumsatellite

Command name: SATELLITE_COMMAND_DESCRIPTOR