ILIntegration // MCP Server Setup

MCP Server Setup & Configuration

How to connect IsounivLib to an MCP (Model Context Protocol) client, the exposed tool surface, and the security model for sustained worldline interventions.

Setup & configuration documentation - endpoint values are examples/placeholders. No MCP server is deployed or connected.
Overview

This page documents how IsounivLib could be connected as an MCP server. It is setup and configuration reference material only. The endpoint values shown are examples and placeholders - they are not live, configured, or connected endpoints. Replace them with the real transport URL and token provided by your deployment before use.

The exposed tools mirror the v1.1 operation pipeline: read the cosmology and telemetry, validate and submit interventions, and audit the intervention log. Every write is validated, idempotent, and gated by human approval where severity requires it.

Client Configuration

MCP clients are configured through an mcpServers object. Three transport styles are supported by the MCP spec:

stdioSpawns a local process and speaks JSON-RPC over stdin/stdout. Best for local, bundled tooling.
SSEServer-Sent Events over a single HTTP connection. An earlier remote transport style.
Streamable HTTPThe current remote style: HTTP POST requests with an SSE response stream. Recommended for hosted servers.

Poke (Shirone) / Lab Connect

Configure the server under the mcpServers key of your Poke / Lab Connect MCP settings. The URL below is a placeholder example.

{
  "mcpServers": {
    "isounivlib": {
      "type": "streamable-http",
      "url": "https://isounivlib.cyanide.poke.site/mcp",  // EXAMPLE placeholder
      "headers": {
        "Authorization": "Bearer <YOUR_API_TOKEN>"        // replace with real token
      }
    }
  }
}

Claude Desktop

Edit claude_desktop_config.json.

{
  "mcpServers": {
    "isounivlib": {
      "command": "npx",
      "args": ["-y", "isounivlib-mcp"],
      "env": {
        "ISounivLib_API_TOKEN": "<YOUR_API_TOKEN>",   // EXAMPLE placeholder
        "ISounivLib_BASE_URL": "https://isounivlib.cyanide.poke.site" // EXAMPLE
      }
    }
  }
}

Cursor

Edit .cursor/mcp.json in your project.

{
  "mcpServers": {
    "isounivlib": {
      "type": "sse",
      "url": "https://isounivlib.cyanide.poke.site/mcp/sse", // EXAMPLE placeholder
      "headers": {
        "Authorization": "Bearer <YOUR_API_TOKEN>"            // replace
      }
    }
  }
}

Custom client

Any MCP-compatible client accepts the same shape. Use the transport that fits your runtime.

{
  "mcpServers": {
    "isounivlib": {
      "type": "streamable-http",              // or "sse" / "stdio"
      "url": "https://isounivlib.cyanide.poke.site/mcp", // EXAMPLE placeholder
      "headers": {
        "Authorization": "Bearer <YOUR_API_TOKEN>"
      }
    }
  }
}
Tool Schemas & Usage

Six tools are exposed. Read tools are open; write tools route through the validated operation pipeline.

get_universe_data

Fetch the entire cosmology tree, optionally filtered by system or worldline.

Parameters
ParamTypeNotes
system_idstringOptional. Filter to one system, e.g. S0218
worldlinestringOptional. Filter to a worldline timestamp
region_idstringOptional. Fetch a single region
Request
{
  "system_id": "S0218",
  "worldline": "P0:S0218:A3:2024:06:17:00:41:22.0002"
}
Response
{
  "systems": [
    {
      "id": "S0218",
      "name": "Std0218",
      "planets": [ { "id": "S0218-IV", "regions": [ { "id": "Hx-Ano-3", "nameCn": "溶洞古校" } ] } ]
    }
  ]
}
get_worldline_telemetry

Query heterogeneity, resonance, stability, and observer state for a worldline.

Parameters
ParamTypeNotes
worldlinestringTarget worldline timestamp
system_idstringOptional. Filter by system
region_idstringOptional. Fetch a specific region's telemetry
Request
{
  "worldline": "P0:S0218:A3:2024:06:17:01:22:04.0031"
}
Response
{
  "telemetry": {
    "heterogeneity": 78,
    "resonance": 64,
    "stability": 41,
    "observer_state": "CONTAINED",
    "sampled_at": "2026-08-26T14:30:00+08:00",
    "sampled_worldline": "P0:S0218:A3:2024:06:17:01:22:04.0031"
  }
}
validate_operation

Submit an operation draft for schema validation, risk check, and impact preview. No write occurs.

Parameters
ParamTypeNotes
actionstringCommand name or custom.* directive
worldlinestringTarget worldline timestamp
actorstringActing entity, e.g. SUSTAINER-07
levelenumINFO / WARN / CRITICAL / BLOCKER
expected_revisionnumberOptional. Concurrency control
payloadobjectOptional. Directive payload
Request
{
  "action": "SURFACE_ROLL_CALL",
  "worldline": "P0:S0218:A3:2024:06:17:00:41:22.0002",
  "actor": "SUSTAINER-07",
  "level": "WARN",
  "expected_revision": 1
}
Response
{
  "valid": true,
  "request_id": "req_1724680000_4821",
  "state": "validated",
  "risk_analysis": { "severity": "low", "requires_approval": true }
}
submit_operation

Submit an approved intervention command. Requires an idempotency_key; returns a request_id.

Parameters
ParamTypeNotes
actionstringCommand name or custom.* directive
worldlinestringTarget worldline timestamp
actorstringActing entity
levelenumSeverity level
idempotency_keystringRequired. Prevents duplicate execution
request_idstringOptional. Client-supplied correlation id
requires_approvalbooleanOptional. Force approval gate
Request
{
  "action": "SURFACE_ROLL_CALL",
  "worldline": "P0:S0218:A3:2024:06:17:00:41:22.0002",
  "actor": "SUSTAINER-07",
  "level": "WARN",
  "idempotency_key": "key_8f3a91",
  "requires_approval": true
}
Response
{
  "request_id": "op_1724680000_4821",
  "idempotency_key": "key_8f3a91",
  "status": "accepted",
  "state": "approval_required"
}
get_operation_status

Check the execution status and logs of a submitted operation.

Parameters
ParamTypeNotes
request_idstringRequired. The operation request_id
Request
{
  "request_id": "op_1724680000_4821"
}
Response
{
  "request_id": "op_1724680000_4821",
  "state": "applied",
  "log": [
    { "state": "queued", "at": "2026-08-26T14:30:00+08:00" },
    { "state": "executing", "at": "2026-08-26T14:30:01+08:00" },
    { "state": "applied", "at": "2026-08-26T14:30:02+08:00" }
  ]
}
get_intervention_logs

Retrieve historical intervention records from intervention_logs.

Parameters
ParamTypeNotes
limitnumberOptional. Max records, default 50
actorstringOptional. Filter by actor
actionstringOptional. Filter by action
resultstringOptional. Filter by result
Request
{
  "actor": "SUSTAINER-07",
  "limit": 10
}
Response
{
  "interventions": [
    {
      "log_id": "INT-HX-0042",
      "worldline": "P0:S0218:A3:2024:06:17:00:41:22.0002",
      "actor": "SUSTAINER-07",
      "level": "WARN",
      "action": "SURFACE_ROLL_CALL",
      "result": "APPROVED"
    }
  ]
}
Authentication & Security

The MCP server authenticates every request with an API token sent as a Bearer header. Access is scoped by role-based clearance levels.

Bearer tokenSend Authorization: Bearer <token>. Tokens are scoped to a clearance level and never exposed to the browser.
Clearance C1 - C5C1 is public reference; C5 is maximum classification. Write tools require C4+; destructive or high-severity actions require C5.
Safe handlingTokens live only in server-side configuration. Never commit secrets or place them in client-side code.
Human approvalHigh-severity operations enter approval_required and wait for a human operator before execution.

Example authenticated request

{
  "mcpServers": {
    "isounivlib": {
      "type": "streamable-http",
      "url": "https://isounivlib.cyanide.poke.site/mcp",  // EXAMPLE placeholder
      "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" }
    }
  }
}

Clearance matrix: C1 read-only reference, C2 read + telemetry, C3 read + validate, C4 submit low-severity interventions, C5 approve and execute high-severity interventions.

Custom Directive Support

Custom worldline intervention instructions are packaged as structured MCP parameters under the custom.interference.directive action. The directive body is carried in the payload and validated before execution.

{
  "action": "custom.interference.directive",
  "worldline": "P0:S0218:A3:2024:06:17:00:41:22.0002",
  "actor": "SUSTAINER-07",
  "level": "WARN",
  "expected_revision": 1,
  "payload": {
    "directive": "cross-reference roll-call register against guild records",
    "scope": "Hx-Ano#3",
    "interference": "LOW"
  }
}

Any action beginning with custom. is routed through the same validated pipeline. The payload must be a structured object; free-form strings are rejected.

Operational Safety Notes
Validate before submitAlways call validate_operation before submit_operation. Validation returns the risk analysis and impact preview.
IdempotencyAlways supply an idempotency_key on submit. Retries with the same key never double-execute.
Expected revisionPass expected_revision to prevent overwriting a document that changed since you read it.
Approval gateTreat approval_required as a hard stop. Do not bypass it for WARN, CRITICAL, or BLOCKER operations.
Audit trailEvery intervention is recorded to intervention_logs with actor, level, action, and result. Review before and after.
PlaceholdersAll URLs and tokens in this documentation are examples. Replace them with real, provisioned values before connecting.