New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

mcp-bridge-cloud

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

mcp-bridge-cloud

Persistent cloud tunnels for MCP servers - CLI tool for connecting local MCP servers to mcp-bridge.xyz

latest
Source
npmnpm
Version
0.1.0
Version published
Maintainers
1
Created
Source

mcp-bridge-cloud

Persistent cloud tunnels for MCP servers

npm version License: MIT

What is this?

mcp-bridge-cloud is a CLI tool that gives your local MCP server a persistent HTTPS URL that never changes.

No more updating ChatGPT configuration every time you restart your server!

# Install globally
npm install -g mcp-bridge-cloud

# Run with your API key
mcp-bridge-cloud --api-key YOUR_API_KEY

# Get a persistent URL like:
# https://yourusername.mcp-bridge.xyz

Features

  • Persistent URLs - Same HTTPS URL across all restarts
  • Zero Configuration - Works out of the box
  • Secure - API key authentication
  • Fast - Low-latency WebSocket tunnel
  • Filesystem MCP - Built-in filesystem server
  • ChatGPT Ready - Compatible with ChatGPT Developer Mode

Installation

npm install -g mcp-bridge-cloud

Quick Start

1. Get API Key

Sign up at https://mcp-bridge.xyz/dashboard and copy your API key.

2. Run the CLI

mcp-bridge-cloud --api-key YOUR_API_KEY

Output:

╔═══════════════════════════════════════════════════════════╗
║              MCP Bridge Cloud                             ║
║         Persistent Tunnels for MCP Servers                ║
╚═══════════════════════════════════════════════════════════╝

🚀 Starting MCP filesystem adapter...
   Root directory: /Users/you/projects
   Port: 3000
✓ Adapter running

🌐 Connecting to MCP Bridge Cloud...
✓ Connected to cloud
   Your persistent URL: https://yourusername.mcp-bridge.xyz

═══════════════════════════════════════════════════════════
✓ Server Ready!
═══════════════════════════════════════════════════════════

📋 Configuration:
   Adapter Port: 3000
   Root Directory: /Users/you/projects
   Subdomain: yourusername
   Persistent URL: https://yourusername.mcp-bridge.xyz

🎯 Next Steps:

   1. Copy your persistent URL:
      https://yourusername.mcp-bridge.xyz

   2. Add to ChatGPT:
      • Settings → Apps & Connectors → Developer Mode
      • Add Remote MCP Server
      • URL: https://yourusername.mcp-bridge.xyz
      • Protocol: HTTP (streaming)
      • Authentication: None

   3. Your URL persists across restarts!
      No need to reconfigure ChatGPT every time ✨

────────────────────────────────────────────────────────────
Press Ctrl+C to stop

3. Add to ChatGPT

  • Open ChatGPT
  • Go to SettingsApps & ConnectorsDeveloper Mode
  • Click Add Remote MCP Server
  • Enter your persistent URL: https://yourusername.mcp-bridge.xyz
  • Select HTTP (streaming)
  • Click Connect

Done! Your MCP server is now available in ChatGPT.

Usage

Basic Usage

# Use default settings (current directory, port 3000)
mcp-bridge-cloud --api-key YOUR_API_KEY

Custom Directory

# Serve a specific directory
mcp-bridge-cloud --api-key YOUR_API_KEY --dir ~/Documents

Custom Port

# Use a different port
mcp-bridge-cloud --api-key YOUR_API_KEY --port 3001

Environment Variables

# Set API key via environment variable
export MCP_CLOUD_API_KEY=YOUR_API_KEY
mcp-bridge-cloud

Debug Mode

# Enable verbose logging
mcp-bridge-cloud --api-key YOUR_API_KEY --debug

Command Line Options

OptionAliasDescriptionDefault
--api-key <key>-kAPI key from mcp-bridge.xyzRequired
--port <number>-pPort for HTTP adapter3000
--dir <path>-dRoot directory to serveCurrent directory
--tunnel-url <url>-tCloud server URLwss://mcp-bridge.xyz
--debugEnable debug loggingfalse
--help-hShow help

Environment Variables

VariableDescription
MCP_CLOUD_API_KEYAPI key (alternative to --api-key)
MCP_CLOUD_URLCloud server URL
DEBUG=1Enable debug mode

How It Works

┌─────────────────────────────────────────────────────────────┐
│ Your Local Machine                                          │
│                                                             │
│  ┌──────────────────┐         ┌──────────────────┐        │
│  │ MCP Server       │ ←────── │ HTTP Adapter     │        │
│  │ (STDIO)          │         │ (port 3000)      │        │
│  └──────────────────┘         └────────┬─────────┘        │
│                                         │                   │
│                                         │ WebSocket         │
└─────────────────────────────────────────┼───────────────────┘
                                          │
                                          ▼
                                ┌──────────────────────┐
                                │ mcp-bridge.xyz       │
                                │ (Cloud Relay)        │
                                └──────────┬───────────┘
                                           │
                                           │ HTTPS
                                           ▼
                                ┌──────────────────────┐
                                │ ChatGPT              │
                                └──────────────────────┘
  • MCP Server runs locally (filesystem access via STDIO)
  • HTTP Adapter wraps it with HTTP interface
  • Cloud Connector establishes WebSocket tunnel to mcp-bridge.xyz
  • ChatGPT connects to your persistent URL
  • Requests flow through cloud → WebSocket → adapter → MCP server

MCP Tools Available

The built-in filesystem server provides these tools:

  • search - Find files by pattern
  • fetch - Read file contents
  • list - List directory contents
  • write - Create or update files

Troubleshooting

"API key required" error

Problem: No API key provided

Solution:

# Provide via command line
mcp-bridge-cloud --api-key YOUR_KEY

# Or via environment variable
export MCP_CLOUD_API_KEY=YOUR_KEY
mcp-bridge-cloud

"Connection refused" error

Problem: Port already in use

Solution:

# Use a different port
mcp-bridge-cloud --api-key YOUR_KEY --port 3001

"MCP server not ready" error

Problem: MCP server failed to start

Solution:

# Check if npx works
npx -y @modelcontextprotocol/server-filesystem --help

# Try with debug mode
mcp-bridge-cloud --api-key YOUR_KEY --debug

Examples

Basic Filesystem Access

# Share your Documents folder with ChatGPT
mcp-bridge-cloud --api-key abc123 --dir ~/Documents

Then in ChatGPT:

You: "List all markdown files in my Documents folder"
ChatGPT: *uses the 'search' tool* "I found 15 markdown files..."

Project Collaboration

# Share a specific project
cd ~/projects/my-app
mcp-bridge-cloud --api-key abc123

Then in ChatGPT:

You: "Read the README.md file"
ChatGPT: *uses the 'fetch' tool* "Here's what I found in your README..."

License

MIT © articat

Support

Made with ❤️ for the MCP community

Keywords

mcp

FAQs

Package last updated on 01 Nov 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts