Server data from the Official MCP Registry
Official MCP server for Lovable, the AI-powered full-stack app builder.
Official MCP server for Lovable, the AI-powered full-stack app builder.
Remote endpoints: streamable-http: https://mcp.lovable.dev
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.
This plugin requests these system permissions. Most are normal for its category.
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"
}
}
}From the project's GitHub README.
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.
https://mcp.lovable.dev
Transport: Streamable HTTP.
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>.
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 mcp add --transport http lovable https://mcp.lovable.dev
Add to claude_desktop_config.json:
{
"mcpServers": {
"lovable": {
"type": "http",
"url": "https://mcp.lovable.dev"
}
}
}
Add the URL directly — no client ID needed:
https://mcp.lovable.dev
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"
}
}
}
}
{
"servers": {
"lovable": {
"type": "http",
"url": "https://mcp.lovable.dev",
"auth": {
"CLIENT_ID": "6d465f583e1e4ce5801b1616f735670c"
}
}
}
}
codex mcp add lovable --url https://mcp.lovable.dev
codex mcp login lovable
Use the same type: http + url + auth.CLIENT_ID shape as the Cursor example above.
The server exposes tools across these areas:
Heads up:
create_projectandsend_messageconsume Lovable build credits.deploy_projectpublishes a public URL.query_databaseruns SQL directly against your project's database.
See the Lovable MCP documentation for the full tool reference.
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.
| Symptom | Fix |
|---|---|
401 Unauthorized / expired token | Re-run your client's login flow to refresh the OAuth token |
| OAuth window loops or never completes | Confirm the client passes the auth.CLIENT_ID shown above |
| "Transport not supported" | The client must support Streamable HTTP |
Tool fails on a missing workspace_id | Call list_workspaces first and pass the returned ID |
This repository hosts the server.json entry for the MCP registry.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.