MCP tool reference

Read tools/list for the exact schema exposed by your token. The tool names below match LinkRunway's public MCP server. Tool annotations describe behavior; they do not replace your approval of consequential changes.

Setup tools

Tool	Input	Effect
`get_setup_status`	`{}`	Reads workspace setup and real event evidence; no full credentials or customer records
`get_integration_guide`	`{ platform }`	Reads installation and consent instructions for `web`, `react-native`, `expo`, `ios`, `android`, or `server`
`verify_setup_event`	`{ eventId }`	Reads evidence for the exact setup CUSTOM event; ID is 1–200 characters
`create_publishable_key`	`{ name }`	Creates a client key; trimmed name 1–100 characters; returns the full key once
`register_mobile_app`	Mobile app fields below	Creates an app registration with real platform identifiers
`create_setup_link`	`{ title, url }`	Creates a labeled demo link without partner commission; title 1–120 characters and HTTP(S) URL
`preview_branch_links`	`{ links, fallbackUrl, iosUrl?, androidUrl?, domainId? }`	Validates and maps Branch link JSON without creating links or fetching URLs

The three setup creation tools are not idempotent. Inspect existing state before retrying an uncertain creation. Demo links consume normal link allowance, and mobile registrations are subject to app limits.

Register a mobile app

Supply name (trimmed, 1–100 characters) and at least one complete platform configuration:

iOS: iosBundleId and iosTeamId. The team ID is exactly 10 uppercase letters or digits.
Android: androidPackage and androidFingerprints. Fingerprints are SHA-256 values with 32 colon-separated hexadecimal bytes; at most 10 fingerprints.

Use the actual identifiers and signing certificates from your application. An Android package without fingerprints or an iOS bundle without a team ID is incomplete. Supplying both complete platforms is supported.

Production link tools

These four tools appear only when the token was issued with production link management enabled.

Tool	Input	Effect
`list_links`	Optional `page`, `limit`, `search`	Reads workspace links using the REST pagination rules
`get_link`	`{ id }`	Reads one workspace link
`create_link`	Link creation fields, including stable `key`	Creates a production link; identical retries return the same link
`update_link`	`{ id, changes }`	Updates named fields, including archive state; existing URLs and QR codes can be affected

The link ID must be 1–100 characters. Link field bounds and ownership validation match the server links reference. Domain IDs must belong to the workspace and be verified; partner IDs must refer to active workspace partners.

Read the existing link before changing it. Review the proposed destination, key, partner, expiry, and archive status. update_link is annotated as destructive because it changes an existing public entry point.

Prompts and resources

prompts/get with name setup_linkrunway returns the platform setup runbook. No prompt arguments are required.
resources/read with URI linkrunway://setup/guide returns the integration guide as application/json.

The runbook asks for real application verification. It should not be used to generate fabricated setup evidence.

Call and read a tool

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "get_setup_status",
    "arguments": {}
  }
}

Tool results contain content text blocks. Successful application data is serialized JSON inside the text. Failures can return isError: true with a human-readable message even when the transport itself succeeded. Check JSON-RPC errors first, then isError, then decode the successful text payload.

Never paste a returned publishable key into a public issue or a shared transcript. MCP cannot return existing full keys, create server keys, browse customer identities, or process payments.