lavela

io.github.ym2629Published by GitHub account ym2629v1.1.1Updated Oct 24, 2026

Deploy a repo to a live app from chat: servers, Postgres, domain, email, Stripe, security scan.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Lets an assistant deploy a repository into a live app, provisioning servers, Postgres, a domain, email, Stripe, and a security scan.

What you can do
Lavela is a remote MCP endpoint that turns a repository into a running application from chat. According to its description, it covers deployment of servers, a Postgres database, a domain, email, Stripe, and a security scan as part of the same flow. No individual tools are listed in the supplied manifest, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to take a project from source code to a hosted, publicly reachable app without leaving the conversation. It is aimed at provisioning the surrounding pieces of a web app, such as database, domain, email, and payments, rather than only pushing code.
Requirements
A remote streamable HTTP endpoint at console.lavela.dev; no local package or runtime is declared. The manifest declares no authentication, environment variables, or headers, but the homepage is a console, so an account there may be needed in practice.
Before you install
The description covers actions that create and change live infrastructure, including servers, a database, a domain, email, and Stripe payments, so expect real resources and possibly real spending. The manifest declares no authentication, so verify how the endpoint is secured and who can reach it before connecting. No tool list is published, so confirm what it can modify or delete.

Installation

In SourceWeft

  1. Open lavela in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ym2629%2Flavela/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lavela": {
      "type": "http",
      "url": "https://console.lavela.dev/api/mcp"
    }
  }
}

README

lavela

Deploy an app from a GitHub repo to a live server, from chat.

lavela is a remote MCP server. Your AI agent (Claude, Claude Code, Cursor, or any MCP client that supports remote servers) builds your repo on a managed server, gives you a live URL, keeps it running, and helps you operate it: logs, captured errors, health checks, managed Postgres, a custom domain you already own, email authentication, and Stripe checkout links.

This repository contains documentation only. lavela's source code is not published here. The service runs at console.lavela.dev. lavela is in beta.

Connect

Add this URL to your MCP client, then sign in with your lavela account when the client opens the browser (OAuth, no token to paste):

https://console.lavela.dev/api/mcp

That connection has the core tools: deploy a repo and operate it. For every tool (ads, schedules, preview environments, security scans, volumes, jobs) use:

https://console.lavela.dev/api/mcp/all

Claude (web, desktop, mobile): Customize → Connectors → Add custom connector → paste the URL.

Claude Code:

bash
claude mcp add --transport http lavela https://console.lavela.dev/api/mcp

Claude Code, Cursor, Windsurf, Claude Desktop in one step:

bash
npx @lavela/cli connect

Install as a plugin

Claude Code — adds the connector and a skill that guides your agent through deploying and checking an app:

bash
claude plugin marketplace add ym2629/lavela-mcpclaude plugin install lavela@lavela-mcp

In one step inside a session: /plugin install lavela --marketplace ym2629/lavela-mcp

Cursor — add the lavela MCP server (one-click link), or add the URL above in Cursor's MCP settings.

Replit — add lavela (one-click link).

Lovable — use the period-free URL https://console.lavela.dev/api/mcp/compat (Connectors → Custom → MCP server → paste the URL → sign in). Lovable rejects tool names that contain a period, so the default URL registers no tool there; this one serves the same core tools named like lavela_account_status. Tested on 2026-10-20: connected, and a read-only call returned the account status.

Mistral Le Chat — open Connectors (under Context in the current app), add a custom connector, and paste the URL above. Le Chat detects OAuth and opens lavela's sign-in page; after you allow the connection, the lavela tools are available in chat. Tested on 2026-10-19; menu names differ slightly between Le Chat versions.

The one-click links follow the formats documented by Cursor and Replit. If one does not open, add the URL manually as described under Connect.

Also from lavela: lavela-preflight, a free read-only checklist plugin for Claude Code that reviews any app before you deploy it. It does not need lavela.

Try it

Start a new conversation and ask:

  • "Check my lavela account status."
  • "Analyze this repo and tell me how lavela would deploy it: https://github.com/OWNER/REPO"
  • "Deploy my GitHub repo OWNER/REPO and give me the live URL."
  • "Is my app up? Show me the latest logs and errors."

What your agent can do

  • Deploy: analyze a repo, build it from GitHub (public repos, or private repos you connect), run web apps and APIs on managed servers, rebuild after you push.
  • Data: managed Postgres, write-only encrypted secrets, one-off jobs.
  • Operate: logs, captured errors, health checks, start / stop / always-on controls, and a one-call overview of each project.
  • Go live: connect a custom domain you already own (DNS only), set up email authentication (DKIM, SPF, DMARC), connect your own Stripe account and create checkout links. Your own sales settle to you in full.

The full, current tool list is always at console.lavela.dev/llms.txt and console.lavela.dev/docs/mcp.

Safety

  • Every tool declares whether it only reads or changes things.
  • Tools that spend money or delete things tell the agent to confirm with you first, and deleting a project requires its exact name.
  • Adding funds always happens in your browser on lavela's site, never through the agent.
  • lavela never edits your source code.

Use it from your own repo

Paste this into your project's AGENTS.md or CLAUDE.md so a coding agent knows how to deploy with lavela:

markdown
## Deploying with lavelaThis app can be deployed with the lavela MCP server (https://console.lavela.dev/api/mcp).- Start with `lavela.account_status`, then run `lavela.analyze_stack` on this repo.- Confirm any cost with the user before calling tools that spend money, such as `lavela.provision_compute_from_repo`.- Never ask for secrets in chat or read `.env` values: use `lavela.env_link` for a local `.env` and `lavela.set_compute_secret` for single secrets.- After deploying, `lavela.project_overview` shows URLs, server state and builds in one call.

Pricing

Servers are paid from a prepaid wallet, billed by the second. New accounts may receive a limited welcome credit. Current prices: console.lavela.dev/pricing.

Links

Support

Email [email protected]. For problems with this documentation, open an issue here.

Source: README.md at commit 5d795f9

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.1.1LatestOct 20, 2026
  2. v1.1.0Oct 6, 2026
  3. v1.0.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts