Back to MCP directory
publicPublicdnsLocal runtime

hostbridge-mcp

一个帮助新手开发者通过对话界面部署Web应用的MCP服务器,弥合了大语言模型和各种托管环境之间的差距。

article

README

Arc MCP Server

A Model Context Protocol (MCP) server that simplifies framework deployments on various hosting environments, with a focus on shared hosting.

Overview

Arc bridges the gap between Large Language Models (LLMs) and hosting environments, allowing novice developers to deploy web applications easily through conversational interfaces. It implements the Model Context Protocol (MCP) to expose tools, resources, and prompts that guide users through the deployment process.

Key Features

  • Framework Support: Deploy Wasp applications with ease, with planned support for more frameworks
  • Multi-Provider: Support for Netlify, Vercel, traditional shared hosting environments, and Hostm.com
  • Guided Deployments: Prompts to guide users through the deployment process
  • Authentication Management: Secure storage of hosting provider credentials
  • Troubleshooting: Built-in tools to diagnose and fix common deployment issues
  • Focused on Shared Hosting: Simplified deployment to traditional shared hosting environments

Status

This project is currently in early development. Contributions and feedback are welcome!

Getting Started

Prerequisites

  • Python 3.10+
  • MCP Client (e.g., Claude Desktop)
  • Hosting provider accounts as needed

Installation

# Clone the repository
git clone https://github.com/elblanco2/arc-mcp.git
cd arc-mcp

# Create a virtual environment
python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate

# Install dependencies
pip install -r requirements.txt

# Install the package in development mode
pip install -e .

Configuration

Create a .env file with your configuration:

SECURE_STORAGE_PATH=~/.arc/credentials

Usage

Running from command line

# Start the server directly
arc

# With debug logging
arc --debug

# With a custom storage path
arc --secure-storage-path=/path/to/credentials

Using with Claude Desktop

  1. Edit your Claude Desktop configuration file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  2. Add Arc server configuration:

{
  "mcpServers": {
    "arc": {
      "command": "python",
      "args": [
        "-m",
        "arc",
        "--debug"
      ]
    }
  }
}
  1. Restart Claude Desktop.

  2. Start conversations with Claude about deploying your applications!

Architecture

Arc is built on a modular architecture:

  • Credentials Manager: Securely stores and retrieves provider credentials
  • Framework Handlers: Framework-specific deployment logic
  • Hosting Providers: Provider-specific deployment operations
  • MCP Interface: Exposes tools, resources, and prompts via the Model Context Protocol

Supported Providers

| Provider | Status | Features | |----------|--------|------------| | Netlify | ✅ Complete | Serverless, Edge, Forms | | Vercel | ✅ Complete | Serverless, Edge, Analytics | | Shared Hosting | ✅ Complete | SSH/SFTP, PHP, MySQL | | Hostm.com | ✅ Complete | Shared Hosting, API Access |

Supported Frameworks

| Framework | Status | Features | |-----------|--------|------------| | Wasp | ✅ Complete | Full-Stack JS Framework | | Next.js | 🚧 Planned | React Framework | | Astro | 🚧 Planned | Static Site Generator |

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Development

# Install development dependencies
pip install -e ".[dev]"

# Run tests
pytest

# Run linting
flake8

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client