MCP.so
登录
L

LivePort MCP Server

@dundas

基本信息

关于 LivePort MCP Server

Give AI agents access to your localhost dev server. Zero-config tunnel that works with Claude Code, OpenClaw, and any MCP-compatible agent. No interstitial pages, no account required.

LivePort MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "liveport": {
      "command": "npx",
      "args": [
        "@liveport/mcp"
      ]
    }
  }
}

LivePort MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

点击上方按钮,在临时沙箱中运行此服务器并实时获取工具列表。

概览

What is LivePort MCP?

LivePort MCP is a secure tunneling tool that creates temporary URLs for applications running on your localhost. It provides key-based authentication and an Agent SDK, enabling AI coding assistants (like Claude, Cursor, etc.) to wait for and access these tunnels for testing.

How to use LivePort MCP?

To use LivePort MCP, install the CLI globally with npm install -g @liveport/cli, obtain a bridge key from app.liveport.dev, and create a tunnel with liveport connect <port> --key <bridge-key>. For AI agent integration, install @liveport/agent-sdk and call agent.waitForTunnel() in your TypeScript code.

Key features of LivePort MCP

  • Secure temporary localhost tunnels with key-based authentication
  • CLI for manual tunnel creation and management
  • Agent SDK for AI coding assistants (e.g., Claude, Cursor)
  • Cross-platform CLI commands (connect, status, disconnect)
  • Programmatic tunnel waiting with configurable timeout and polling

Use cases of LivePort MCP

  • AI coding assistants testing web applications on a developer’s localhost
  • Running end‑to‑end tests against a tunneled local server
  • Collaborative debugging by sharing a temporary public URL of a local service
  • Integrating automated test suites that need to reach a development server

常见问题

1

What is the difference between LivePort MCP and traditional ngrok/localhost.run?

LivePort MCP is built specifically for AI agents, providing a dedicated Agent SDK that lets agents wait for a tunnel to be ready rather than requiring developers to manually share a URL. It uses key-based authentication and temporary tunnels.

2

What are the runtime requirements for LivePort MCP?

The CLI and Agent SDK require Node.js and npm. The tunnel server infrastructure uses Node.js, PostgreSQL, Redis, and is hosted on Cloudflare and Fly.io.

3

Where does data live when using LivePort MCP?

Tunnel traffic passes through a tunnel server (based on a LocalTunnel fork). The tunnels are temporary; authentication uses a bridge key managed via the dashboard. No user application data is persisted by the tunnel server.

4

What are the known limits of LivePort MCP?

The README does not specify explicit limits. Tunnels have an expiry time (visible via the `expiresAt` field in the Agent SDK). The CLI and SDK assume Node.js environments.

5

What transport and authentication does LivePort MCP use?

All communication uses HTTPS. Authentication is performed via a bridge key (string starting with `lpk_`) provided at tunnel creation and during agent SDK initialization.

评论

AI 与智能体 分类下的更多 MCP 服务器