Lovable

dev.lovablePublished by lovable.devOfficial publisherv0.1.3Updated Oct 24, 2026

Official MCP server for Lovable, the AI-powered full-stack app builder.

VerifiedStreamable HTTPWeb executableDatabasesCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Official Lovable MCP server that lets an assistant create, edit, deploy and manage Lovable full-stack app projects over OAuth-secured Streamable HTTP.

What you can do
  • List, create, deploy, remix and inspect projects and workspaces, and manage their visibility
  • Send messages to a project's AI agent and retrieve its responses
  • Inspect code through diffs, file trees, file contents and edit history
  • Read and write project or workspace AI instructions
  • Enable and query a project's Postgres database and get connection info
  • Manage connectors and external MCP integrations, browse templates, view traffic analytics and generate upload URLs
When to use it
Useful when you want to drive Lovable app building from Claude, Cursor, Codex, ChatGPT or another MCP client: scaffolding a project, iterating on it through the AI agent, reviewing diffs and publishing a live URL without leaving the chat.
Requirements
Remote endpoint at using Streamable HTTP; the client must support that transport. OAuth 2.1 login is required, and clients other than Claude, Claude Code and ChatGPT must also pass Lovable's public OAuth client ID in their auth config. A Lovable account with build credits is needed for project creation and agent messages.
Before you install
create_project and send_message consume Lovable build credits, so assistant actions can spend paid quota. deploy_project publishes a public URL, query_database runs SQL directly against your project database, and knowledge tools write AI instructions, so changes are live. Connector tools can add or remove external integrations such as Linear, Notion and Slack. Tokens are bearer tokens; re-login when they expire.

Installation

In SourceWeft

  1. Open Lovable 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/dev.lovable%2Fmcp/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": {
    "lovable": {
      "type": "http",
      "url": "https://mcp.lovable.dev/"
    }
  }
}

README

Lovable MCP

The official Model Context Protocol server for Lovable, an AI-powered full-stack app builder.

Connect Claude, Cursor, Codex, and other MCP-compatible clients to Lovable so they can create, edit, deploy, and manage Lovable projects through natural language.

Endpoint

https://mcp.lovable.dev

Transport: Streamable HTTP.

Authentication

OAuth 2.1. MCP clients discover the authorization server via RFC 9728 metadata at https://mcp.lovable.dev/.well-known/oauth-protected-resource and obtain a bearer token automatically. The token is passed as Authorization: Bearer <token>.

Install

Claude, Claude Code, and ChatGPT need only the URL. Any other client must also pass Lovable's public OAuth client ID (6d465f583e1e4ce5801b1616f735670c), shown below.

Claude Code

sh
claude mcp add --transport http lovable https://mcp.lovable.dev

Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "lovable": {      "type": "http",      "url": "https://mcp.lovable.dev"    }  }}

ChatGPT

Add the URL directly — no client ID needed:

https://mcp.lovable.dev

Cursor / Windsurf

Add to your client's MCP config (~/.cursor/mcp.json, or Windsurf's mcp_config.json):

json
{  "mcpServers": {    "lovable": {      "type": "http",      "url": "https://mcp.lovable.dev",      "auth": {        "CLIENT_ID": "6d465f583e1e4ce5801b1616f735670c"      }    }  }}

VS Code

json
{  "servers": {    "lovable": {      "type": "http",      "url": "https://mcp.lovable.dev",      "auth": {        "CLIENT_ID": "6d465f583e1e4ce5801b1616f735670c"      }    }  }}

Codex CLI

sh
codex mcp add lovable --url https://mcp.lovable.devcodex mcp login lovable

Other clients

Use the same type: http + url + auth.CLIENT_ID shape as the Cursor example above.

Tools

The server exposes tools across these areas:

  • Projects & workspaces — list, create, deploy, remix, inspect; manage visibility
  • Agent interaction — send messages to a project's AI agent and retrieve responses
  • Code inspection — diffs, file tree, file contents, edit history
  • Knowledge — read and write project / workspace AI instructions
  • Cloud database — enable a Postgres database, check status, run SQL, get connection info
  • Connectors & MCP servers — list, add, and remove external integrations (Linear, Notion, Slack, custom MCP, …)
  • Templates & libraries — browse template and library projects
  • Analytics — historical and real-time project traffic
  • File uploads — generate upload URLs for attaching images

Heads up: create_project and send_message consume Lovable build credits. deploy_project publishes a public URL. query_database runs SQL directly against your project's database.

See the Lovable MCP documentation for the full tool reference.

Common workflow

Build and deploy a new app:

1. list_workspaces()                       → workspace_id2. create_project(workspace_id, ...)       → project_id   (uses credits)3. send_message(project_id, "Add ...")     → message_id   (uses credits)4. get_diff(project_id, message_id)        → review changes5. deploy_project(project_id)              → live URL

Most tools need a workspace_id — call list_workspaces first. read_file needs a git ref; get latest_commit_sha from get_project.

Troubleshooting

SymptomFix
401 Unauthorized / expired tokenRe-run your client's login flow to refresh the OAuth token
OAuth window loops or never completesConfirm the client passes the auth.CLIENT_ID shown above
"Transport not supported"The client must support Streamable HTTP
Tool fails on a missing workspace_idCall list_workspaces first and pass the returned ID

Registry

This repository hosts the server.json entry for the MCP registry.

License

Apache License 2.0

Source: README.md at commit 0336e6d

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

1
  1. v0.1.3LatestSep 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