linkrunway.
Start for free
LINKRUNWAY × MODEL CONTEXT PROTOCOL

MCP.
Your assistant,
connected.

Give your assistant a direct connection to LinkRunway. Set up an SDK, configure an app, manage links, and verify a real integration—with access you control.

Open your workspace Read the connection guide →

Hosted MCP · Workspace-scoped tokens · 24-hour expiry

Access, made explicit

Choose what your assistant can do.

7 tools · Setup and migration preview

  • get_setup_statusRead
  • get_integration_guideRead
  • verify_setup_eventRead
  • create_publishable_keyWrite
  • register_mobile_appWrite
  • create_setup_linkWrite
  • preview_branch_linksRead

Permission preview only. An owner enables real access when issuing a token in the workspace.

CONNECTION

One endpoint. Explicit authorization.

Sign in as a workspace owner and open Developers → MCP / guided setup. Choose your platform, issue a token, and copy the endpoint and configuration into a compatible MCP client.

Use Streamable HTTP with a custom Bearer header. The hosted endpoint is https://api.linkrunway.com/v1/mcp; use the endpoint supplied by your console if it differs.

Transport
Streamable HTTP · stateless POST
Credential
A dedicated lr_mcp_… token on every request
Accept header
application/json, text/event-stream
Client support
Custom Authorization headers required; OAuth-only and legacy SSE-only clients are unsupported.
sh
# Use a private environment variable containing your lr_mcp_ token.
curl --fail-with-body https://api.linkrunway.com/v1/mcp \
  -H "Authorization: Bearer $LINKRUNWAY_MCP_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

This read-only example lists tools. A standard MCP client performs initialization first. See the handshake example for protocol negotiation.

TOOL REFERENCE

A clear scope for every action.

Read the live tools/list schema before calling a tool. Setup access includes writes; enable production-link access only when your task needs it.

Setup · seven tools

get_setup_statusRead

Inspect workspace configuration and real setup-event evidence.

get_integration_guideRead

Read platform-specific installation and consent instructions.

verify_setup_eventRead

Check whether the exact verification event reached your workspace.

create_publishable_keyWrite

Create a client key and return its full value once.

register_mobile_appWrite

Register real app identifiers and signing information.

create_setup_linkWrite

Create a labeled demo link without a partner commission.

preview_branch_linksRead

Preview supplied Branch link definitions without creating links or fetching URLs.

Production links · four optional tools

list_linksRead

Search and paginate links in the authorized workspace.

get_linkRead

Read one workspace link and its routing configuration.

create_linkWrite

Create a production link with a stable key for safe retries.

update_linkWrite

Change routing, metadata, or archive state on an existing link.

Read all tool inputs, limits, and response formats →

FROM SETUP TO EVIDENCE

Verify the connection in your app.

The assistant can guide configuration. Your application supplies the proof.

  1. 01

    Authorize the task

    Issue an owner-scoped token for the correct workspace. Leave production link management off unless you need it.

  2. 02

    Inspect before creating

    Ask for setup status and the platform guide. Review existing keys, apps, and links before approving a write.

  3. 03

    Run the real application

    After consent, send the exact setup CUSTOM event with metadata.source set to developer_setup.

  4. 04

    Check the result

    Call verify_setup_event with that event ID and inspect the received evidence. Revoke the token when finished.

Let the built-in runbook guide the work.

The setup_linkrunway prompt provides the setup sequence. The linkrunway://setup/guide resource provides the platform guide as JSON. A successful handshake or copied prompt alone does not establish a working app integration.

ACCESS & SAFETY

Keep the workspace in your control.

One workspace, limited lifetime

Tokens expire after 24 hours and can be revoked. The issuer must remain an owner and meet verification and workspace MFA requirements.

Review changes to live links

Optional production-link tools can alter published URLs and QR destinations. Review the destination, partner, expiry, and archive state before a change.

Keep trusted events on your backend

MCP cannot create server keys or report financial events. Your backend verifies payments and customer identity; client SDKs handle consented attribution.

Handle retries deliberately

Stable keys make production link creation retryable. Setup creation tools can create duplicates. Check state after an uncertain response and inspect tool-level isError results.

COMMON QUESTIONS

Before you connect.

What is MCP, and where do the SDKs fit?

Model Context Protocol lets an assistant discover and call tools in LinkRunway. Use it for guided setup and authorized link management. Your SDK still captures consented app activity, and your backend uses the REST API for trusted business events.

Which assistants can connect?

Use an MCP client that supports Streamable HTTP and a custom Authorization header. Copy the endpoint and configuration from Developers in your workspace. OAuth-only connectors and legacy SSE-only clients are not compatible with this connection.

Which platforms have guided setup?

Web, React Native, Expo, iOS, Android, and server integrations have MCP guides. Flutter has a separate SDK guide, but Flutter is not currently a guided-platform value for the MCP tool.

Can an assistant manage existing production links?

Only when an owner issues the token with production link management enabled. That adds list_links, get_link, create_link, and update_link. Review proposed changes: updating a link can affect URLs and QR codes already in circulation.

Can MCP access payments or create server keys?

No. MCP cannot create server keys, report financial events, or administer billing. Payment verification and authoritative customer identity remain on your backend. Keep server keys out of assistant prompts and client applications.

How long does access last?

A token is bound to one workspace and expires after 24 hours. Revoke it in the console when finished. The issuer must remain an owner and satisfy email-verification and workspace MFA requirements. Creating another token does not revoke older tokens automatically.

What counts as a verified integration?

Run the exact CUSTOM verification event from your actual application after consent, with metadata.source set to developer_setup. Then ask verify_setup_event to check that event ID. A handshake, copied prompt, or newly created key alone does not prove the app is connected.

Do setup tools change data or use plan allowances?

Creating a publishable key, registering an app, and creating a demo link write real workspace data. Link and app allowances still apply. These setup creation tools are not idempotent: inspect existing state before repeating an uncertain request.

GO DEEPER

The complete integration path.

Use MCP alongside the SDKs and server API. These guides cover the configuration, contracts, and checks for each part.

Connect with MCP

Tokens, headers, handshake, and troubleshooting.

MCP tool reference

Inputs, permissions, prompts, resources, and errors.

Migrate links

Preview Branch exports and review mappings before creating links.

Choose an SDK

All six SDKs, release-pinned installs, and platform guides.

REST API

Server links, trusted events, client endpoints, and retries.

Test your integration

Real app evidence, consent, webhooks, and launch checks.

Browse the public documentation repository ↗