Connect with MCP

LinkRunway's Model Context Protocol server lets an assistant inspect setup, retrieve SDK instructions, register an app, and verify an event from your real application. Optional production-link tools can also create and update links in the authorized workspace.

Issue a token

1. Sign in to the console as a workspace owner.
2. Open Developers and the MCP / guided setup controls.
3. Choose the platform and copy the generated endpoint and connection configuration.
4. Leave production link management disabled unless the assistant needs to manage live links.
5. Store the lr_mcp_… token in the MCP client's protected configuration.

The token is scoped to one workspace, expires after 24 hours, and can be revoked in the console. The issuer must remain an owner and meet email-verification and workspace MFA requirements. A suspended workspace cannot use it. Issuing another token does not revoke existing tokens.

The guided platforms are web, React Native, Expo, iOS, Android, and server. Flutter has a public SDK guide, but is not currently a guided-platform value for get_integration_guide.

Client requirements

Use an MCP client supporting Streamable HTTP with a custom Authorization header. The endpoint is /v1/mcp on the API endpoint supplied by the console. The hosted API endpoint also accepts this route at https://api.linkrunway.com/v1/mcp.

OAuth-only connectors and legacy SSE-only clients are not compatible with this configuration. Do not treat a GET request returning 405 as evidence that MCP is down. JSON-RPC batches are rejected. A command-line client should omit Origin; a supplied Origin must match the console origin.

Check the handshake

Set LINKRUNWAY_MCP_TOKEN privately. This example uses a read-only initialization request; use the protocol version your MCP client negotiates.

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":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"integration-check","version":"1.0.0"}}}'

A standard MCP client then sends notifications/initialized. Notifications can return HTTP 202 with no JSON body. Because the endpoint is stateless, send Authorization on every subsequent request.

Inspect available tools

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":2,"method":"tools/list","params":{}}'

A normal setup token exposes seven tools. A token with production link management exposes eleven. Read the live inputSchema before invoking a tool, and read the tool reference to understand which calls write data.

Verify the actual application

Ask the assistant to read get_setup_status, retrieve the platform guide, and follow the setup_linkrunway prompt. Run the supplied verification event in the real app after consent. It must be the exact CUSTOM event ID expected by setup, with metadata.source equal to developer_setup.

Then call verify_setup_event with that event ID. A key, copied prompt, successful handshake, or tool invocation alone is not proof of runtime integration. The assistant should report the received event evidence and any untested platform steps explicitly.

Revoke the token after setup. Keep payment verification and server secrets in your backend. MCP cannot create server keys, report financial events, or administer billing.

Connection failures

401 usually means a missing, expired, or revoked MCP token. 403 can mean the issuer's role or security requirements no longer qualify, an Origin mismatch, or an explicit workspace header that disagrees with the token. 405 means the wrong HTTP method. A successful HTTP response can still contain a JSON-RPC error or isError: true; inspect both layers.

Protocol reference: MCP Streamable HTTP specification.