Skip to content
Loophole

Install for other clients

The connection, in plain terms

Section titled “The connection, in plain terms”

Loophole is a standard MCP server on a Streamable HTTP transport, bound to loopback. Any MCP client connects with three facts from bridge.json:

  • transport: http (Streamable HTTP)
  • url: http://127.0.0.1:<port>/mcp
  • header: Authorization: Bearer <token>

Most clients express this as an mcpServers map identical to the Claude Desktop and Cursor blocks:

{
  "mcpServers": {
    "loophole": {
      "transport": "http",
      "url": "http://127.0.0.1:<port>/mcp",
      "headers": { "Authorization": "Bearer <token-from-bridge.json>" }
    }
  }
}

If your client speaks stdio only, it cannot connect directly; the bridge is HTTP-in-host by design (the Extension Host owns stdio). Use a client that supports an http or streamable-http transport.

Check the protocol without a client

Section titled “Check the protocol without a client”

The MCP Inspector confirms the server answers before you wire any editor:

Terminal window
npx @modelcontextprotocol/inspector
# connect to http://127.0.0.1:<port>/mcp with the bearer token, then run tools/list

A healthy server lists 12 tools.

Verify it worked

Section titled “Verify it worked”
  1. Live 12.4.5b Suite is running with the Loophole extension active.
  2. Your client (or the Inspector) lists the Loophole tools.
  3. Run live_get_song_overview (or live_find_track) and confirm it returns your real track names.

If the tool returns your actual tracks, the connection is correct. Otherwise see Troubleshooting.