Back to Browse

Mcp MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://mcp.lovable.dev

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "dev-lovable-mcp": {
      "url": "https://mcp.lovable.dev"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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

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

Claude Desktop

Add to claude_desktop_config.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):

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

VS Code

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

Codex CLI

codex mcp add lovable --url https://mcp.lovable.dev
codex 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_id
2. 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 changes
5. 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

Reviews

No reviews yet

Be the first to review this server!